Automation system user interface

ABSTRACT

Systems and methods include an automation network comprising a gateway at a premises. The gateway is coupled to a remote network and is configured to control components at the premises including at least one of a thermostat and a lock. A sensor user interface (SUI) is coupled to the gateway and presented to a user via remote client devices. The SUI includes display elements for managing and receiving data of the components agnostically across the remote client devices. The display elements include an interactive icon comprising control regions. Each control region is configured to control a state change of a corresponding component.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a divisional application of U.S. patent applicationSer. No. 15/238,864, filed Aug. 17, 2016, now abandoned, which is herebyincorporated by reference in its entirety.

U.S. patent application Ser. No. 15/238,864, claims the benefit of U.S.Patent Application No. 62/205,922, filed Aug. 17, 2015;

and claims the benefit of U.S. Patent Application No. 62/205,872, filedAug. 17, 2015;

and is a continuation in part application of U.S. patent applicationSer. No. 12/189,780, filed Aug. 11, 2008, now abandoned;

and is a continuation in part application of U.S. patent applicationSer. No. 13/531,757, filed Jun. 25, 2012, now abandoned;

and is a continuation in part application of U.S. patent applicationSer. No. 12/197,958, filed Aug. 25, 2008, now U.S. Pat. No. 10,721,087;

and is a continuation in part application of U.S. patent applicationSer. No. 13/334,998, filed Dec. 22, 2011, now U.S. Pat. No. 9,531,593;

and is a continuation in part application of U.S. patent applicationSer. No. 12/539,537, filed Aug. 11, 2009, now U.S. Pat. No. 10,156,959;

and is a continuation in part application of U.S. patent applicationSer. No. 14/645,808, filed Mar. 12, 2015, now U.S. Pat. No. 10,127,801;

and is a continuation in part application of U.S. patent applicationSer. No. 13/104,932, filed May 10, 2011, now abandoned;

and is a continuation in part application of U.S. patent applicationSer. No. 13/104,936, filed May 10, 2011, now U.S. Pat. No. 10,380,871;

and is a continuation in part application of U.S. patent applicationSer. No. 13/929,568, filed Jun. 27, 2013, now U.S. Pat. No. 10,444,964;

and is a continuation in part application of U.S. patent applicationSer. No. 14/704,045, filed May 5, 2015, now U.S. Pat. No. 10,365,810;

and is a continuation in part application of U.S. patent applicationSer. No. 14/704,098, filed May 5, 2015, now U.S. Pat. No. 10,348,575;

and is a continuation in part application of U.S. patent applicationSer. No. 14/704,127, filed May 5, 2015, now abandoned;

and is a continuation in part application of U.S. patent applicationSer. No. 14/628,651, filed Feb. 23, 2015, now U.S. Pat. No. 10,091,014;

and is a continuation in part application of U.S. patent applicationSer. No. 13/718,851, filed Dec. 18, 2012, now U.S. Pat. No. 10,156,831;

and is a continuation in part application of U.S. patent applicationSer. No. 12/972,740, filed Dec. 20, 2010, now U.S. Pat. No. 9,729,342;

and is a continuation in part application of U.S. patent applicationSer. No. 13/954,553, filed Jul. 30, 2013, now U.S. Pat. No. 11,582,065;

and is a continuation in part application of U.S. patent applicationSer. No. 14/943,162, filed Nov. 17, 2015, now U.S. Pat. No. 10,062,245;

and is a continuation in part application of U.S. patent applicationSer. No. 15/177,915, filed Jun. 9, 2016, now U.S. Pat. No. 11,316,958;

and is a continuation in part application of U.S. patent applicationSer. No. 15/177,448, filed Jun. 9, 2016;

and is a continuation in part application of U.S. patent applicationSer. No. 15/196,281, filed Jun. 29, 2016, now U.S. Pat. No. 11,368,327;

and is a continuation in part application of U.S. patent applicationSer. No. 15/198,531, filed Jun. 30, 2016, now abandoned;

and is a continuation in part application of U.S. patent applicationSer. No. 15/204,662, filed Jul. 7, 2016, now U.S. Pat. No. 10,522,026;

and is a continuation in part application of U.S. patent applicationSer. No. 15/237,873, filed Aug. 16, 2016.

TECHNICAL FIELD

The embodiments described herein relate generally to a method andapparatus for improving the capabilities of home automation systems inpremises applications.

BACKGROUND

The field of home and small business security is dominated by technologysuppliers who build comprehensive ‘closed’ security systems, where theindividual components (sensors, security panels, keypads) operate solelywithin the confines of a single vendor solution. For example, a wirelessmotion sensor from vendor A cannot be used with a security panel fromvendor B. Each vendor typically has developed sophisticated proprietarywireless technologies to enable the installation and management ofwireless sensors, with little or no ability for the wireless devices tooperate separate from the vendor's homogeneous system. Furthermore,these traditional systems are extremely limited in their ability tointerface either to a local or wide area standards-based network (suchas an IP network); most installed systems support only a low-bandwidth,intermittent connection utilizing phone lines or cellular (RF) backupsystems. Wireless security technology from providers such as GESecurity, Honeywell, and DSC/Tyco are well known in the art, and areexamples of this proprietary approach to security systems for home andbusiness.

Furthermore, with the proliferation of the internet, ethernet and WiFilocal area networks (LANs) and advanced wide area networks (WANs) thatoffer high bandwidth, low latency connections (broadband), as well asmore advanced wireless WAN data networks (e.g. GPRS or CDMA 1×RTT) thereincreasingly exists the networking capability to extend thesetraditional security systems to offer enhanced functionality. Inaddition, the proliferation of broadband access has driven acorresponding increase in home and small business networkingtechnologies and devices. It is desirable to extend traditional securitysystems to encompass enhanced functionality such as the ability tocontrol and manage security systems from the world wide web, cellulartelephones, or advanced function internet-based devices. Other desiredfunctionality includes an open systems approach to interface homesecurity systems to home and small business networks.

Due to the proprietary approach described above, the traditional vendorsare the only ones capable of taking advantage of these new networkfunctions. To date, even though the vast majority of home and businesscustomers have broadband network access in their premises, most securitysystems do not offer the advanced capabilities associated with highspeed, low-latency LANs and WANs. This is primarily because theproprietary vendors have not been able to deliver such technologyefficiently or effectively. Solution providers attempting to addressthis need are becoming known in the art, including three categories ofvendors: traditional proprietary hardware providers such as Honeywelland GE Security; third party hard-wired module providers such asAlarm.com, NextAlarm, and uControl; and new proprietary systemsproviders such as InGrid.

A disadvantage of the prior art technologies of the traditionalproprietary hardware providers arises due to the continued proprietaryapproach of these vendors. As they develop technology in this area itonce again operates only with the hardware from that specific vendor,ignoring the need for a heterogeneous, cross-vendor solution. Yetanother disadvantage of the prior art technologies of the traditionalproprietary hardware providers arises due to the lack of experience andcapability of these companies in creating open internet and web basedsolutions, and consumer friendly interfaces.

A disadvantage of the prior art technologies of the third partyhard-wired module providers arises due to the installation andoperational complexities and functional limitations associated withhardwiring a new component into existing security systems. Moreover, adisadvantage of the prior art technologies of the new proprietarysystems providers arises due to the need to discard all priortechnologies, and implement an entirely new form of security system toaccess the new functionalities associated with broadband and wirelessdata networks. There remains, therefore, a need for systems, devices,and methods that easily interface to and control the existingproprietary security technologies utilizing a variety of wirelesstechnologies.

INCORPORATION BY REFERENCE

Each patent, patent application, and/or publication mentioned in thisspecification is herein incorporated by reference in its entirety to thesame extent as if each individual patent, patent application, and/orpublication was specifically and individually indicated to beincorporated by reference.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of the integrated security system, under anembodiment.

FIG. 2 is a block diagram of components of the integrated securitysystem, under an embodiment.

FIG. 3 is a block diagram of the gateway software or applications, underan embodiment.

FIG. 4 is a block diagram of the gateway components, under anembodiment.

FIG. 5 (collectively FIGS. 5A and 5B) shows the orb icon andcorresponding text summary display elements, under an embodiment.

FIG. 6 is a table of security state and the corresponding sensor statusdisplayed on the SUI, under an embodiment.

FIG. 7 is a table of system state and the corresponding warning textdisplayed as system warnings on the SUI, under an embodiment.

FIG. 8 is a table of sensor state/sort order and the correspondingsensor name and status text of the SUI, under an embodiment.

FIG. 9 shows icons of the interesting sensors, under an embodiment.

FIG. 10 shows the quiet sensor icon, under an embodiment.

FIG. 11 is an example Home Management Mode (HMM) screen presented viathe web portal SUI, under an embodiment.

FIG. 12 is an example Home Management Mode (HMM) screen presented viathe mobile portal SUI, under an embodiment.

FIG. 13 is a block diagram of an iPhone® client device SUI, under anembodiment.

FIG. 14 is a first example iPhone® client device SUI, under anembodiment.

FIG. 15 is a second example iPhone® client device SUI, under anembodiment.

FIG. 16 is a block diagram of a mobile portal client device SUI, underan embodiment.

FIG. 17 is an example summary page or screen presented via the mobileportal SUI, under an embodiment.

FIG. 18 is an example security panel page or screen presented via themobile portal SUI, under an embodiment.

FIG. 19 is an example sensor status page or screen presented via themobile portal SUI, under an embodiment.

FIG. 20 is an example interface page or screen presented via the webportal SUI, under an embodiment.

FIG. 21 is an example summary page or screen presented via thetouchscreen SUI, under an embodiment.

FIG. 22 is an example sensor status page or screen presented via thetouchscreen SUI, under an embodiment.

FIG. 23 is an example Home View display, under an embodiment.

FIG. 24 shows a table of sensor icons displayed on the Home View floorplan, under an embodiment.

FIG. 25 shows example device icons of Home View, under an embodiment.

FIG. 26 shows a Home View display that includes indicators for multiplefloors, under an embodiment.

FIG. 27 shows the system states along with the corresponding Home Viewdisplay and system or orb icon, under an embodiment.

FIG. 28 shows a Home View floor display (disarmed) that includes awarning indicator, under an embodiment.

FIG. 29 shows an example of the Home View using the iPhone security tab,under an embodiment.

FIG. 30 shows an example screen for site Settings, under an embodiment.

FIG. 31 shows an example screen for Security Tab Options, under anembodiment.

FIG. 32 shows an example “Add Floor” screen for use in selecting a floorplan, under an embodiment.

FIG. 33 shows an “Edit Home View” screen of the editor, under anembodiment.

FIG. 34 shows an example of dragging a device icon during which a nameof the device (“Front Door”) is displayed, under an embodiment.

FIG. 35 is an example of a U-shaped floor plan customized by changinginterior tiles to define walls, under an embodiment.

FIG. 36 shows an example in which the zoom level is increased anddragging has been used to focus on a sensor location, under anembodiment.

FIG. 37 is an example “Add Floor” page, under an embodiment.

FIG. 38 is an example Edit Home View screen showing the floor thumbnailsfor use in selecting a floor, under an embodiment.

FIG. 39 shows the Edit Home View screen with a delete floor selector,under an embodiment.

FIG. 40 is an example Edit Home View screen displaying options to “Save”and “Don't Save” changes following selection of the Done button, underan embodiment.

FIG. 41 is an example of the floor grid data, under an embodiment.

FIG. 42 is an example sensor hash table for a single-floor site, underan embodiment.

FIG. 43 shows an example hash table mapping, under an embodiment.

FIG. 44 shows the twelve shapes of a tile set, under an embodiment.

FIG. 45 shows the tile shapes and corresponding fill options forrendered tiles, under an embodiment.

FIG. 46 is an example tile rendering for a room of a premise, under anembodiment.

FIG. 47 is an example popup display in response to hoveringnear/adjacent a sensor icon (e.g., “Garage” sensor), under anembodiment.

FIG. 48 shows a Home View display that includes a floor plan display4800 of a selected floor along with indicators 4801/4802 for multiplefloors, under an embodiment.

FIG. 49 shows an example of the Home View user interface displayed via amobile device (e.g., iPhone), under an embodiment.

Home View is configured via site settings as described in detail herein.Each application retains or remembers the user's preferred mode acrosssessions.

FIG. 50 shows an example of a Settings page of Home View, under anembodiment.

FIG. 51 shows an example “Home View Setup” editor page 5100 for use inselecting a floor plan, under an embodiment.

FIG. 52 shows a “Home View Setup” editor screen 5200 with a selectedfloor plan 5201, under an embodiment.

FIG. 59 shows a Home View Setup page 5900 with options displayed, underan embodiment.

FIG. 53 shows an example editor screen 5300 for which a label 5301 witha name of the device (“Front Door”) is displayed, under an embodiment.

FIG. 54 shows a Home View Setup page 5400 with a selected floor plan5201 that has been edited to add numerous interior walls 5401, under anembodiment.

FIG. 55 shows a Home View Setup page with a label editing prompt 5501,under an embodiment.

FIG. 56 shows a Home View Setup page 5600 in a zoomed editing mode tozoom on one room 5601 in a building, under an embodiment.

FIG. 57 shows a Home View Setup page for adding at least one floor to afloor plan, under an embodiment.

FIG. 58 shows a Home View Setup page 5800 with editing for multiplefloors, under an embodiment.

FIG. 60 shows a Home View Setup page 6000 with editor exit optionprompts 6001 displayed, under an embodiment.

FIG. 61 is an example floor plan, under an embodiment.

FIG. 62 is an example Home View one-story floor plan, under anembodiment.

FIG. 63 is an example Home View floor plan that includes two devices,under an embodiment.

FIG. 64 is an example Home View floor plan that includes two labels,under an embodiment.

FIG. 65 is a block diagram of IP device integration with a premisenetwork, under an embodiment.

FIG. 66 is a block diagram of IP device integration with a premisenetwork, under an alternative embodiment.

FIG. 67 is a block diagram of a touchscreen, under an embodiment.

FIG. 68 is an example screenshot of a networked security touchscreen,under an embodiment.

FIG. 69 is a block diagram of network or premise device integration witha premise network, under an embodiment.

FIG. 70 is a block diagram of network or premise device integration witha premise network, under an alternative embodiment.

FIG. 71 is a flow diagram for a method of forming a security networkincluding integrated security system components, under an embodiment.

FIG. 72 is a flow diagram for a method of forming a security networkincluding integrated security system components and network devices,under an embodiment.

FIG. 73 is a flow diagram for installation of an IP device into aprivate network environment, under an embodiment.

FIG. 74 is a block diagram showing communications among IP devices ofthe private network environment, under an embodiment.

FIG. 75 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment.

FIG. 76 is a block diagram of an integrated security system wirelesslyinterfacing to proprietary security systems, under an embodiment.

FIG. 77 is a flow diagram for wirelessly ‘learning’ the gateway into anexisting security system and discovering extant sensors, under anembodiment.

FIG. 78 is a block diagram of a security system in which the legacypanel is replaced with a wireless security panel wirelessly coupled to agateway, under an embodiment.

FIG. 79 is a block diagram of a security system in which the legacypanel is replaced with a wireless security panel wirelessly coupled to agateway, and a touchscreen, under an alternative embodiment.

FIG. 80 is a block diagram of a security system in which the legacypanel is replaced with a wireless security panel connected to a gatewayvia an Ethernet coupling, under another alternative embodiment.

FIG. 81 is a flow diagram for automatic takeover of a security system,under an embodiment.

FIG. 82 is a flow diagram for automatic takeover of a security system,under an alternative embodiment.

FIG. 83 is an example status interface of Home View 3D, under anembodiment.

FIG. 84 is an example user interface of Home View 3D, under anembodiment.

FIG. 85 is an example user interface showing “enable” control of HomeView 3D, under an embodiment.

FIG. 86 is an example user interface showing “disable” control of HomeView 3D, under an embodiment.

FIG. 87 is an example editor interface with indicators of Home View 3Dbeing enabled, under an embodiment.

FIG. 88 is an example user interface showing five floors, under anembodiment.

FIG. 89 is an example interface of Home View 3D showing variables, underan embodiment.

FIG. 90 shows example renderings for square, wide, and tall canvases, 2Dsingle floor, and 2D multi floor, under an embodiment.

FIG. 91 is an example user interface showing a “heat map” of Home View3D, under an embodiment.

FIG. 92 is an example user interface for configuring a “heat map” ofHome View 3D, under an embodiment.

FIG. 93 is another example user interface for configuring a “heat map”of Home View 3D, under an embodiment.

FIG. 94 is an example UI screen, under an embodiment.

FIG. 95 shows an example Status Bar of the UI, under an embodiment.

FIG. 96 shows an example System Bar of the UI, under an embodiment.

FIG. 97 shows an example Tab Bar of the UI, under an embodiment.

FIG. 98 shows an example Details View of the UI, under an embodiment.

FIG. 99 shows two versions of an example Details Card in Home View ofthe UI, under an embodiment.

FIG. 100 shows an example List View of the UI, under an embodiment.

FIG. 101 shows an example List layout of List View of the UI, under anembodiment.

FIG. 102 shows a device list item of the UI, under an embodiment.

FIG. 103 shows an example Settings Menu of the UI, under an embodiment.

FIG. 104 shows an example Events History View of the UI, under anembodiment.

FIG. 105 shows example thermostat line graphs of the UI, under anembodiment.

FIG. 106 shows example versions of a dismissable message in a messagebar of the UI, under an embodiment.

FIG. 107 shows example versions of a non-dismissable message in amessage bar of the UI, under an embodiment.

FIG. 108 shows example versions of multiple messages presented by theUI, under an embodiment.

FIG. 109 shows example versions of a Home View (3D, multiple floors)screen or page of the UI, under an embodiment.

FIG. 110 shows an example Home View (2D, multiple floors) screen or pageof the UI, under an embodiment.

FIG. 111 shows an example Home View device control screen or page of theUI, under an embodiment.

FIG. 112 shows an example Notable Events screen or page of the UI, underan embodiment.

FIG. 113 shows example versions of a sensor list screen or page of theUI, under an embodiment.

FIG. 114 shows an example Sensor History screens or pages of the UI,under an embodiment.

FIG. 115 shows an example of arm options presented by the UI, under anembodiment.

FIG. 116 shows an example of arm protest presented by the UI, under anembodiment.

FIG. 117 shows an example of arm protest failed presented by the UI,under an embodiment.

FIG. 118 shows an example of arm dialogue presented by the UI, under anembodiment.

FIG. 119 shows an example of modes dialog presented by the UI, under anembodiment.

FIG. 120 shows examples of camera detail screens presented by the UI,under an embodiment.

FIG. 121 shows example camera device lists presented by the UI, under anembodiment.

FIG. 122 shows an example of camera full-screen live video presented bythe UI, under an embodiment.

FIG. 123 shows camera capture options (e.g., “Take Picture”, “Take VideoClip”, etc.) presented by the UI, under an embodiment.

FIG. 124 shows a capture message (e.g., “Capturing Video Clip . . . ”)presented by the UI, under an embodiment.

FIG. 125 shows example camera history (clips and pictures) viewspresented by the UI, under an embodiment.

FIG. 126A shows an example binary switch icon (“off” state) presented bythe UI, under an embodiment.

FIG. 126B shows an example binary switch icon (“on” state, indicated bydifferent color than “off” state) presented by the UI, under anembodiment.

FIG. 127A shows an example UI page with a binary switch (e.g., coffeemaker, etc.) icon (“off” state) presented by the UI, under anembodiment.

FIG. 127B shows an example UI page with a binary switch (e.g., coffeemaker, etc.) icon (“on” state, indicated by different color than “off”state) presented by the UI, under an embodiment.

FIG. 128A shows an example dimmer switch icon (“off” state) presented bythe UI, under an embodiment.

FIG. 128B shows an example dimmer switch icon (“on” state, indicated bydifferent color than “off” state) presented by the UI, under anembodiment.

FIG. 128C shows an example dimmer switch icon (in use) presented by theUI, under an embodiment.

FIG. 129A shows an example UI page with a dimmer switch (e.g., light,etc.) icon “off” state) presented by the UI, under an embodiment.

FIG. 129B shows an example UI page with a dimmer switch (e.g., light,etc.)

icon (“on” state, indicated by different color than “off” state)presented by the UI, under an embodiment.

FIGS. 130A and 130B show example thermostat state icons presented by theUI, under an embodiment.

FIG. 131 shows set point drag and tap areas of a thermostat presented bythe UI, under an embodiment.

FIG. 132 shows the thermostat set point (heat/cool) slider in use (top),and increment/decrement function in use (bottom) as presented by the UI,under an embodiment.

FIG. 133A shows example versions of thermostat details (auto mode)screens presented by the UI, under an embodiment.

FIG. 133B shows an example thermostat (actively heating) screenpresented by the UI, under an embodiment.

FIG. 133C shows an example thermostat (actively cooling) screenpresented by the UI, under an embodiment.

FIG. 133D shows an example thermostat (changing cool setpoint) screenpresented by the UI, under an embodiment.

FIG. 133E shows an example thermostat (off) screen presented by the UI,under an embodiment.

FIG. 134 shows mode selection popups presented by the UI, under anembodiment.

FIG. 135 shows an example door lock control tap and drag control screenpresented by the UI, under an embodiment.

FIG. 136 shows example lock icons (e.g., locked state, unlocked state,low battery) presented by the UI, under an embodiment.

FIG. 137A shows an example UI with door lock details icon (inactive)presented by the UI, under an embodiment.

FIG. 137B shows an example UI page with door lock details icon (active)presented by the UI, under an embodiment.

FIG. 138A shows an example UI page with garage door details icon(inactive) presented by the UI, under an embodiment.

FIG. 138B shows an example UI page with garage door details icon(active) presented by the UI, under an embodiment.

FIG. 139 shows an example energy meter details page of the UI, under anembodiment.

DETAILED DESCRIPTION

Systems and methods include an automation network comprising a gatewayat a premises. The gateway is coupled to a remote network and isconfigured to control components at the premises including at least oneof a thermostat and a lock. A sensor user interface (SUI) is coupled tothe gateway and presented to a user via remote client devices. The SUIincludes display elements for managing and receiving data of thecomponents agnostically across the remote client devices. The displayelements include an interactive icon comprising control regions. Eachcontrol region is configured to control a state change of acorresponding component.

An integrated security system is described that integrates broadband andmobile access and control with conventional security systems and premisedevices to provide a tri-mode security network (broadband, cellular/GSM,POTS access) that enables users to remotely stay connected to theirpremises. The integrated security system, while delivering remotepremise monitoring and control functionality to conventional monitoredpremise protection, complements existing premise protection equipment.The integrated security system integrates into the premise network andcouples wirelessly with the conventional security panel, enablingbroadband access to premise security systems. Automation devices(cameras, lamp modules, thermostats, etc.) can be added, enabling usersto remotely see live video and/or pictures and control home devices viatheir personal web portal or webpage, mobile phone, and/or other remoteclient device. Users can also receive notifications via email or textmessage when happenings occur, or do not occur, in their home.

Although the detailed description herein contains many specifics for thepurposes of illustration, anyone of ordinary skill in the art willappreciate that many variations and alterations to the following detailsare within the scope of the embodiments described herein. Thus, thefollowing illustrative embodiments are set forth without any loss ofgenerality to, and without imposing limitations upon, the claimedinvention.

In accordance with the embodiments described herein, a wireless system(e.g., radio frequency (RF)) is provided that enables a securityprovider or consumer to extend the capabilities of an existingRF-capable security system or a non-RF-capable security system that hasbeen upgraded to support RF capabilities. The system includes anRF-capable Gateway device (physically located within RF range of theRF-capable security system) and associated software operating on theGateway device. The system also includes a web server, applicationserver, and remote database providing a persistent store for informationrelated to the system.

The security systems of an embodiment, referred to herein as theiControl security system or integrated security system, extend the valueof traditional home security by adding broadband access and theadvantages of remote home monitoring and home control through theformation of a security network including components of the integratedsecurity system integrated with a conventional premise security systemand a premise local area network (LAN). With the integrated securitysystem, conventional home security sensors, cameras, touchscreenkeypads, lighting controls, and/or Internet Protocol (IP) devices in thehome (or business) become connected devices that are accessible anywherein the world from a web browser, mobile phone or through content-enabledtouchscreens. The integrated security system experience allows securityoperators to both extend the value proposition of their monitoredsecurity systems and reach new consumers that include broadband usersinterested in staying connected to their family, home and property whenthey are away from home.

The integrated security system of an embodiment includes securityservers (also referred to herein as iConnect servers or security networkservers) and an iHub gateway (also referred to herein as the gateway,the iHub, or the iHub client) that couples or integrates into a homenetwork (e.g., LAN) and communicates directly with the home securitypanel, in both wired and wireless installations. The security system ofan embodiment automatically discovers the security system components(e.g., sensors, etc.) belonging to the security system and connected toa control panel of the security system and provides consumers with fulltwo-way access via web and mobile portals. The gateway supports variouswireless protocols and can interconnect with a wide range of controlpanels offered by security system providers. Service providers and userscan then extend the system's capabilities with the additional IPcameras, lighting modules or security devices such as interactivetouchscreen keypads. The integrated security system adds an enhancedvalue to these security systems by enabling consumers to stay connectedthrough email and SMS alerts, photo push, event-based video capture andrule-based monitoring and notifications. This solution extends the reachof home security to households with broadband access.

The integrated security system builds upon the foundation afforded bytraditional security systems by layering broadband and mobile access, IPcameras, interactive touchscreens, and an open approach to homeautomation on top of traditional security system configurations. Theintegrated security system is easily installed and managed by thesecurity operator, and simplifies the traditional security installationprocess, as described below.

The integrated security system provides an open systems solution to thehome security market. As such, the foundation of the integrated securitysystem customer premises equipment (CPE) approach has been to abstractdevices, and allows applications to manipulate and manage multipledevices from any vendor. The integrated security system DeviceConnecttechnology that enables this capability supports protocols, devices, andpanels from GE Security and Honeywell, as well as consumer devices usingZ-Wave, IP cameras (e.g., Ethernet, wifi, and Homeplug), and IPtouchscreens. The DeviceConnect is a device abstraction layer thatenables any device or protocol layer to interoperate with integratedsecurity system components. This architecture enables the addition ofnew devices supporting any of these interfaces, as well as add entirelynew protocols.

The benefit of DeviceConnect is that it provides supplier flexibility.The same consistent touchscreen, web, and mobile user experience operateunchanged on whatever security equipment selected by a security systemprovider, with the system provider's choice of IP cameras, backend datacenter and central station software.

The integrated security system provides a complete system thatintegrates or layers on top of a conventional host security systemavailable from a security system provider. The security system providertherefore can select different components or configurations to offer(e.g., CDMA, GPRS, no cellular, etc.) as well as have iControl modifythe integrated security system configuration for the system provider'sspecific needs (e.g., change the functionality of the web or mobileportal, add a GE or Honeywell-compatible TouchScreen, etc.).

The integrated security system integrates with the security systemprovider infrastructure for central station reporting directly viaBroadband and GPRS alarm transmissions. Traditional dial-up reporting issupported via the standard panel connectivity. Additionally, theintegrated security system provides interfaces for advancedfunctionality to the CMS, including enhanced alarm events, systeminstallation optimizations, system test verification, videoverification, 2-way voice over IP and GSM.

The integrated security system is an IP centric system that includesbroadband connectivity so that the gateway augments the existingsecurity system with broadband and GPRS connectivity. If broadband isdown or unavailable GPRS may be used, for example. The integratedsecurity system supports GPRS connectivity using an optional wirelesspackage that includes a GPRS modem in the gateway. The integratedsecurity system treats the GPRS connection as a higher cost thoughflexible option for data transfers. In an embodiment the GPRS connectionis only used to route alarm events (e.g., for cost), however the gatewaycan be configured (e.g., through the iConnect server interface) to actas a primary channel and pass any or all events over GPRS. Consequently,the integrated security system does not interfere with the current plainold telephone service (POTS) security panel interface. Alarm events canstill be routed through POTS; however the gateway also allows suchevents to be routed through a broadband or GPRS connection as well. Theintegrated security system provides a web application interface to theCSR tool suite as well as XML web services interfaces for programmaticintegration between the security system provider's existing call centerproducts. The integrated security system includes, for example, APIsthat allow the security system provider to integrate components of theintegrated security system into a custom call center interface. The APIsinclude XML web service APIs for integration of existing security systemprovider call center applications with the integrated security systemservice. All functionality available in the CSR Web application isprovided with these API sets. The Java and XML-based APIs of theintegrated security system support provisioning, billing, systemadministration, CSR, central station, portal user interfaces, andcontent management functions, to name a few. The integrated securitysystem can provide a customized interface to the security systemprovider's billing system, or alternatively can provide security systemdevelopers with APIs and support in the integration effort.

The integrated security system provides or includes business componentinterfaces for provisioning, administration, and customer care to name afew. Standard templates and examples are provided with a definedcustomer professional services engagement to help integrate OSS/BSSsystems of a Service Provider with the integrated security system.

The integrated security system components support and allow for theintegration of customer account creation and deletion with a securitysystem. The iConnect APIs provides access to the provisioning andaccount management system in iConnect and provide full support foraccount creation, provisioning, and deletion. Depending on therequirements of the security system provider, the iConnect APIs can beused to completely customize any aspect of the integrated securitysystem backend operational system.

The integrated security system includes a gateway that supports thefollowing standards-based interfaces, to name a few: Ethernet IPcommunications via Ethernet ports on the gateway, and standardXML/TCP/IP protocols and ports are employed over secured SSL sessions;USB 2.0 via ports on the gateway; 802.11b/g/n IP communications;GSM/GPRS RF WAN communications; CDMA 1×RTT RF WAN communications(optional, can also support EVDO and 3G technologies).

The gateway supports the following proprietary interfaces, to name afew: interfaces including Dialog RF network (319.5 MHz) and RS485Superbus 2000 wired interface; RF mesh network (908 MHz); and interfacesincluding RF network (345 MHz) and RS485/RS232bus wired interfaces.

Regarding security for the IP communications (e.g., authentication,authorization, encryption, anti-spoofing, etc), the integrated securitysystem uses SSL to encrypt all IP traffic, using server andclient-certificates for authentication, as well as authentication in thedata sent over the SSL-encrypted channel. For encryption, integratedsecurity system issues public/private key pairs at the time/place ofmanufacture, and certificates are not stored in any online storage in anembodiment.

The integrated security system does not need any special rules at thecustomer premise and/or at the security system provider central stationbecause the integrated security system makes outgoing connections usingTCP over the standard HTTP and HTTPS ports. Provided outbound TCPconnections are allowed then no special requirements on the firewallsare necessary.

FIG. 1 is a block diagram of the integrated security system 100, underan embodiment. The integrated security system 100 of an embodimentincludes the gateway 102 and the security servers 104 coupled to theconventional home security system 110. At a customer's home or business,the gateway 102 connects and manages the diverse variety of homesecurity and self-monitoring devices. The gateway 102 communicates withthe iConnect Servers 104 located in the service provider's data center106 (or hosted in integrated security system data center), with thecommunication taking place via a communication network 108 or othernetwork (e.g., cellular network, internet, etc.). These servers 104manage the system integrations necessary to deliver the integratedsystem service described herein. The combination of the gateway 102 andthe iConnect servers 104 enable a wide variety of remote client devices120 (e.g., PCs, mobile phones and PDAs) allowing users to remotely stayin touch with their home, business and family. In addition, thetechnology allows home security and self-monitoring information, as wellas relevant third party content such as traffic and weather, to bepresented in intuitive ways within the home, such as on advancedtouchscreen keypads.

The integrated security system service (also referred to as iControlservice) can be managed by a service provider via browser-basedMaintenance and Service Management applications that are provided withthe iConnect Servers. Or, if desired, the service can be more tightlyintegrated with existing OSS/BSS and service delivery systems via theiConnect web services-based XML APIs.

The integrated security system service can also coordinate the sendingof alarms to the home security Central Monitoring Station (CMS) 199.Alarms are passed to the CMS 199 using standard protocols such asContact ID or SIA and can be generated from the home security panellocation as well as by iConnect server 104 conditions (such as lack ofcommunications with the integrated security system). In addition, thelink between the security servers 104 and CMS 199 provides tighterintegration between home security and self-monitoring devices and thegateway 102. Such integration enables advanced security capabilitiessuch as the ability for CMS personnel to view photos taken at the time aburglary alarm was triggered. For maximum security, the gateway 102 andiConnect servers 104 support the use of a mobile network (both GPRS andCDMA options are available) as a backup to the primary broadbandconnection.

The integrated security system service is delivered by hosted serversrunning software components that communicate with a variety of clienttypes while interacting with other systems. FIG. 2 is a block diagram ofcomponents of the integrated security system 100, under an embodiment.Following is a more detailed description of the components.

The iConnect servers 104 support a diverse collection of clients 120ranging from mobile devices, to PCs, to in-home security devices, to aservice provider's internal systems. Most clients 120 are used byend-users, but there are also a number of clients 120 that are used tooperate the service.

Clients 120 used by end-users of the integrated security system 100include, but are not limited to, the following:

-   -   Clients based on gateway client applications 202 (e.g., a        processor-based device running the gateway technology that        manages home security and automation devices).    -   A web browser 204 accessing a Web Portal application, performing        end-user configuration and customization of the integrated        security system service as well as monitoring of in-home device        status, viewing photos and video, etc. Device and user        management can also be performed by this portal application.    -   A mobile device 206 (e.g., PDA, mobile phone, etc.) accessing        the integrated security system Mobile Portal. This type of        client 206 is used by end-users to view system status and        perform operations on devices (e.g., turning on a lamp, arming a        security panel, etc.) rather than for system configuration tasks        such as adding a new device or user.    -   PC or browser-based “widget” containers 208 that present        integrated security system service content, as well as other        third-party content, in simple, targeted ways (e.g. a widget        that resides on a PC desktop and shows live video from a single        in-home camera). “Widget” as used herein means applications or        programs in the system.    -   Touchscreen home security keypads 208 and advanced in-home        devices that present a variety of content widgets via an        intuitive touchscreen user interface.    -   Notification recipients 210 (e.g., cell phones that receive        SMS-based notifications when certain events occur (or don't        occur), email clients that receive an email message with similar        information, etc.).    -   Custom-built clients (not shown) that access the iConnect web        services XML API to interact with users' home security and        self-monitoring information in new and unique ways. Such clients        could include new types of mobile devices, or complex        applications where integrated security system content is        integrated into a broader set of application features.

In addition to the end-user clients, the iConnect servers 104 support PCbrowser-based Service Management clients that manage the ongoingoperation of the overall service. These clients run applications thathandle tasks such as provisioning, service monitoring, customer supportand reporting.

There are numerous types of server components of the iConnect servers104 of an embodiment including, but not limited to, the following:Business Components which manage information about all of the homesecurity and self-monitoring devices; End-User Application Componentswhich display that information for users and access the BusinessComponents via published XML APIs; and Service Management ApplicationComponents which enable operators to administer the service (thesecomponents also access the Business Components via the XML APIs, andalso via published SNMP MIBs).

The server components provide access to, and management of, the objectsassociated with an integrated security system installation. Thetop-level object is the “network.” It is a location where a gateway 102is located, and is also commonly referred to as a site or premises; thepremises can include any type of structure (e.g., home, office,warehouse, etc.) at which a gateway 102 is located. Users can onlyaccess the networks to which they have been granted permission. Within anetwork, every object monitored by the gateway 102 is called a device.Devices include the sensors, cameras, home security panels andautomation devices, as well as the controller or processor-based devicerunning the gateway applications.

Various types of interactions are possible between the objects in asystem. Automations define actions that occur as a result of a change instate of a device. For example, take a picture with the front entrycamera when the front door sensor changes to “open”. Notifications aremessages sent to users to indicate that something has occurred, such asthe front door going to “open” state, or has not occurred (referred toas an iWatch notification). Schedules define changes in device statesthat are to take place at predefined days and times. For example, setthe security panel to “Armed” mode every weeknight at 11:00 pm.

The iConnect Business Components are responsible for orchestrating allof the low-level service management activities for the integratedsecurity system service. They define all of the users and devicesassociated with a network (site), analyze how the devices interact, andtrigger associated actions (such as sending notifications to users). Allchanges in device states are monitored and logged. The BusinessComponents also manage all interactions with external systems asrequired, including sending alarms and other related self-monitoringdata to the home security Central Monitoring System (CMS) 199. TheBusiness Components are implemented as portable Java J2EE Servlets, butare not so limited.

The following iConnect Business Components manage the main elements ofthe integrated security system service, but the embodiment is not solimited:

-   -   A Registry Manager 220 defines and manages users and networks.        This component is responsible for the creation, modification and        termination of users and networks. It is also where a user's        access to networks is defined.    -   A Network Manager 222 defines and manages security and        self-monitoring devices that are deployed on a network (site).        This component handles the creation, modification, deletion and        configuration of the devices, as well as the creation of        automations, schedules and notification rules associated with        those devices.    -   A Data Manager 224 manages access to current and logged state        data for an existing network and its devices. This component        specifically does not provide any access to network management        capabilities, such as adding new devices to a network, which are        handled exclusively by the Network Manager 222.    -   To achieve optimal performance for all types of queries, data        for current device states is stored separately from historical        state data (a.k.a. “logs”) in the database. A Log Data Manager        226 performs ongoing transfers of current device state data to        the historical data log tables.

Additional iConnect Business Components handle direct communicationswith certain clients and other systems, for example:

-   -   An iHub Manager 228 directly manages all communications with        gateway clients, including receiving information about device        state changes, changing the configuration of devices, and        pushing new versions of the gateway client to the hardware it is        running on.    -   A Notification Manager 230 is responsible for sending all        notifications to clients via SMS (mobile phone messages), email        (via a relay server like an SMTP email server), etc.    -   An Alarm and CMS Manager 232 sends critical server-generated        alarm events to the home security Central Monitoring Station        (CMS) and manages all other communications of integrated        security system service data to and from the CMS.    -   The Element Management System (EMS) 234 is an iControl Business        Component that manages all activities associated with service        installation, scaling and monitoring, and filters and packages        service operations data for use by service management        applications. The SNMPBs published by the EMS can also be        incorporated into any third party monitoring system if desired.

The iConnect Business Components store information about the objectsthat they manage in the iControl Service Database 240 and in theiControl Content Store 242. The iControl Content Store is used to storemedia objects like video, photos and widget content, while the ServiceDatabase stores information about users, networks, and devices. Databaseinteraction is performed via a JDBC interface. For security purposes,the Business Components manage all data storage and retrieval.

The iControl Business Components provide web services-based APIs thatapplication components use to access the Business Components'capabilities. Functions of application components include presentingintegrated security system service data to end-users, performingadministrative duties, and integrating with external systems andback-office applications.

The primary published APIs for the iConnect Business Components include,but are not limited to, the following:

-   -   A Registry Manager API 252 provides access to the Registry        Manager Business Component's functionality, allowing management        of networks and users.    -   A Network Manager API 254 provides access to the Network Manager        Business Component's functionality, allowing management of        devices on a network.    -   A Data Manager API 256 provides access to the Data Manager        Business Component's functionality, such as setting and        retrieving (current and historical) data about device states.    -   A Provisioning API 258 provides a simple way to create new        networks and configure initial default properties.

Each API of an embodiment includes two modes of access: Java API or XMLAPI. The XML APIs are published as web services so that they can beeasily accessed by applications or servers over a network. The Java APIsare a programmer-friendly wrapper for the XML APIs. Applicationcomponents and integrations written in Java should generally use theJava APIs rather than the XML APIs directly.

The iConnect Business Components also have an XML-based interface 260for quickly adding support for new devices to the integrated securitysystem. This interface 260, referred to as DeviceConnect 260, is aflexible, standards-based mechanism for defining the properties of newdevices and how they can be managed. Although the format is flexibleenough to allow the addition of any type of future device, pre-definedXML profiles are currently available for adding common types of devicessuch as sensors (SensorConnect), home security panels (PanelConnect) andIP cameras (CameraConnect).

The iConnect End-User Application Components deliver the user interfacesthat run on the different types of clients supported by the integratedsecurity system service. The components are written in portable JavaJ2EE technology (e.g., as Java Servlets, as JavaServer Pages (JSPs),etc.) and they all interact with the iControl Business Components viathe published APIs.

The following End-User Application Components generate CSS-basedHTML/JavaScript that is displayed on the target client. Theseapplications can be dynamically branded with partner-specific logos andURL links (such as Customer Support, etc.). The End-User ApplicationComponents of an embodiment include, but are not limited to, thefollowing:

-   -   An iControl Activation Application 270 that delivers the first        application that a user sees when they set up the integrated        security system service. This wizard-based web browser        application securely associates a new user with a purchased        gateway and the other devices included with it as a kit (if        any). It primarily uses functionality published by the        Provisioning API.    -   An iControl Web Portal Application 272 runs on PC browsers and        delivers the web-based interface to the integrated security        system service. This application allows users to manage their        networks (e.g. add devices and create automations) as well as to        view/change device states, and manage pictures and videos.        Because of the wide scope of capabilities of this application,        it uses three different Business Component APIs that include the        Registry Manager API, Network Manager API, and Data Manager API,        but the embodiment is not so limited.    -   An iControl Mobile Portal 274 is a small-footprint web-based        interface that runs on mobile phones and PDAs. This interface is        optimized for remote viewing of device states and        pictures/videos rather than network management. As such, its        interaction with the Business Components is primarily via the        Data Manager API.    -   Custom portals and targeted client applications can be provided        that leverage the same Business Component APIs used by the above        applications.    -   A Content Manager Application Component 276 delivers content to        a variety of clients. It sends multimedia-rich user interface        components to widget container clients (both PC and        browser-based), as well as to advanced touchscreen keypad        clients. In addition to providing content directly to end-user        devices, the Content Manager 276 provides widget-based user        interface components to satisfy requests from other Application        Components such as the iControl Web 272 and Mobile 274 portals.

A number of Application Components are responsible for overallmanagement of the service. These pre-defined applications, referred toas Service Management Application Components, are configured to offeroff-the-shelf solutions for production management of the integratedsecurity system service including provisioning, overall servicemonitoring, customer support, and reporting, for example. The ServiceManagement Application Components of an embodiment include, but are notlimited to, the following:

-   -   A Service Management Application 280 allows service        administrators to perform activities associated with service        installation, scaling and monitoring/alerting. This application        interacts heavily with the Element Management System (EMS)        Business Component to execute its functionality, and also        retrieves its monitoring data from that component via protocols        such as SNMP MIBs.    -   A Kitting Application 282 is used by employees performing        service provisioning tasks. This application allows home        security and self-monitoring devices to be associated with        gateways during the warehouse kitting process.    -   A CSR Application and Report Generator 284 is used by personnel        supporting the integrated security system service, such as CSRs        resolving end-user issues and employees enquiring about overall        service usage. Pushes of new gateway firmware to deployed        gateways is also managed by this application.

The iConnect servers 104 also support custom-built integrations with aservice provider's existing OSS/BSS, CSR and service delivery systems290. Such systems can access the iConnect web services XML API totransfer data to and from the iConnect servers 104. These types ofintegrations can compliment or replace the PC browser-based ServiceManagement applications, depending on service provider needs.

As described above, the integrated security system of an embodimentincludes a gateway, or iHub. The gateway of an embodiment includes adevice that is deployed in the home or business and couples or connectsthe various third-party cameras, home security panels, sensors anddevices to the iConnect server over a WAN connection as described indetail herein. The gateway couples to the home network and communicatesdirectly with the home security panel in both wired and wireless sensorinstallations. The gateway is configured to be low-cost, reliable andthin so that it complements the integrated security system network-basedarchitecture.

The gateway supports various wireless protocols and can interconnectwith a wide range of home security control panels. Service providers andusers can then extend the system's capabilities by adding IP cameras,lighting modules and additional security devices. The gateway isconfigurable to be integrated into many consumer appliances, includingset-top boxes, routers and security panels. The small and efficientfootprint of the gateway enables this portability and versatility,thereby simplifying and reducing the overall cost of the deployment.

FIG. 3 is a block diagram of the gateway 102 including gateway softwareor applications, under an embodiment. The gateway software architectureis relatively thin and efficient, thereby simplifying its integrationinto other consumer appliances such as set-top boxes, routers, touchscreens and security panels. The software architecture also provides ahigh degree of security against unauthorized access. This sectiondescribes the various key components of the gateway softwarearchitecture.

The gateway application layer 302 is the main program that orchestratesthe operations performed by the gateway. The Security Engine 304provides robust protection against intentional and unintentionalintrusion into the integrated security system network from the outsideworld (both from inside the premises as well as from the WAN). TheSecurity Engine 304 of an embodiment comprises one or more sub-modulesor components that perform functions including, but not limited to, thefollowing:

-   -   Encryption including 128-bit SSL encryption for gateway and        iConnect server communication to protect user data privacy and        provide secure communication.    -   Bi-directional authentication between the gateway and iConnect        server in order to prevent unauthorized spoofing and attacks.        Data sent from the iConnect server to the gateway application        (or vice versa) is digitally signed as an additional layer of        security. Digital signing provides both authentication and        validation that the data has not been altered in transit.    -   Camera SSL encapsulation because picture and video traffic        offered by off-the-shelf networked IP cameras is not secure when        traveling over the Internet. The gateway provides for 128-bit        SSL encapsulation of the user picture and video data sent over        the internet for complete user security and privacy.    -   802.11b/g/n with WPA-2 security to ensure that wireless camera        communications always takes place using the strongest available        protection.    -   A gateway-enabled device is assigned a unique activation key for        activation with an iConnect server. This ensures that only valid        gateway-enabled devices can be activated for use with the        specific instance of iConnect server in use. Attempts to        activate gateway-enabled devices by brute force are detected by        the Security Engine. Partners deploying gateway-enabled devices        have the knowledge that only a gateway with the correct serial        number and activation key can be activated for use with an        iConnect server. Stolen devices, devices attempting to        masquerade as gateway-enabled devices, and malicious outsiders        (or insiders as knowledgeable but nefarious customers) cannot        effect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 allows for seamless and secureupdates to the gateway firmware through the iControl MaintenanceApplication on the server 104, providing a transparent, hassle-freemechanism for the service provider to deploy new features and bug fixesto the installed user base. The firmware download mechanism is tolerantof connection loss, power interruption and user interventions (bothintentional and unintentional). Such robustness reduces down time andcustomer support issues. Gateway firmware can be remotely downloadeither for one gateway at a time, a group of gateways, or in batches.

The Automations engine 308 manages the user-defined rules of interactionbetween the different devices (e.g. when door opens turn on the light).Though the automation rules are programmed and reside at theportal/server level, they are cached at the gateway level in order toprovide short latency between device triggers and actions.

DeviceConnect 310 includes definitions of all supported devices (e.g.,cameras, security panels, sensors, etc.) using a standardized plug-inarchitecture. The DeviceConnect module 310 offers an interface that canbe used to quickly add support for any new device as well as enablinginteroperability between devices that use differenttechnologies/protocols. For common device types, pre-defined sub-moduleshave been defined, making supporting new devices of these types eveneasier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules engine 318 is responsible for executing the user definedschedules (e.g., take a picture every five minutes; every day at 8 amset temperature to 65 degrees Fahrenheit, etc.). Though the schedulesare programmed and reside at the iConnect server level they are sent tothe scheduler within the gateway application. The Schedules Engine 318then interfaces with SensorConnect 312 to ensure that scheduled eventsoccur at precisely the desired time.

The Device Management module 320 is in charge of all discovery,installation and configuration of both wired and wireless IP devices(e.g., cameras, etc.) coupled or connected to the system. Networked IPdevices, such as those used in the integrated security system, requireuser configuration of many IP and security parameters—to simplify theuser experience and reduce the customer support burden, the devicemanagement module of an embodiment handles the details of thisconfiguration. The device management module also manages the videorouting module described below.

The video routing engine 322 is responsible for delivering seamlessvideo streams to the user with zero-configuration. Through a multi-step,staged approach the video routing engine uses a combination of UPnPport-forwarding, relay server routing and STUN/TURN peer-to-peerrouting.

FIG. 4 is a block diagram of components of the gateway 102, under anembodiment. Depending on the specific set of functionality desired bythe service provider deploying the integrated security system service,the gateway 102 can use any of a number of processors 402, due to thesmall footprint of the gateway application firmware. In an embodiment,the gateway could include the Broadcom BCM5354 as the processor forexample. In addition, the gateway 102 includes memory (e.g., FLASH 404,RAM 406, etc.) and any number of input/output (I/O) ports 408.

Referring to the WAN portion 410 of the gateway 102, the gateway 102 ofan embodiment can communicate with the iConnect server using a number ofcommunication types and/or protocols, for example Broadband 412, GPRS414 and/or Public Switched Telephone Network (PTSN) 416 to name a few.In general, broadband communication 412 is the primary means ofconnection between the gateway 102 and the iConnect server 104 and theGPRS/CDMA 414 and/or PSTN 416 interfaces acts as backup for faulttolerance in case the user's broadband connection fails for whateverreason, but the embodiment is not so limited.

Referring to the LAN portion 420 of the gateway 102, various protocolsand physical transceivers can be used to communicate to off-the-shelfsensors and cameras. The gateway 102 is protocol-agnostic andtechnology-agnostic and as such can easily support almost any devicenetworking protocol. The gateway 102 can, for example, support GE andHoneywell security RF protocols 422, Z-Wave 424, serial (RS232 andRS485) 426 for direct connection to security panels as well as WiFi 428(802.11b/g) for communication to WiFi cameras.

The system of an embodiment uses or includes a system user interface(SUI) that provides an iconic, at-a-glance representation of securitysystem status. The SUI is for use across all client types as describedabove with reference to FIG. 1 . The SUI includes a number of displayelements that are presented across all types of client devices used tomonitor status of the security system. The clients of an embodimentinclude, but are not limited to, the iPhone, the iPad, a mobile portal,a web portal, and a touchscreen. The display elements of the SUI of anembodiment include, but are not limited to, an orb icon, text summary,security button, device and system warnings, interesting sensors, andquiet sensors, as described in detail below. The SUI thus providessystem status summary information (e.g., security and sensors) uniformlyacross all clients. Additionally, the SUI provides consistenticonography, terminology, and display rules across all clients as wellas consistent sensor and system detail across clients.

Following is a description of the various states of the iControlsensors, and how these states are indicated uniformly across all clientsusing the SUI and other sensor information displays such as sensor listsand timelines.

Regarding the display elements of the SUI, the orb icon visuallyindicates the current arm state and sensor status of a single site. FIG.5 (collectively FIGS. 5A and 5B) shows the orb icon and correspondingtext summary display elements, under an embodiment. Across all clients,when sensor detail is shown in a list or timeline, state is indicatedusing the proper icon, text summary and grouping. The orb icons and textsummary elements of an embodiment generally represent system state 4001to include the following states: “Disarmed” or “Subdisarmed; “Armed(Doors and Windows, Stay, Away, All, Night Stay, Instant, Motion,Maximum)”; “Disarmed”, or “Subdisarmed” (sensor absent; sensor tripped;sensor tampered; low battery; uncleared alarm); “Armed (Doors andWindows, Stay, Away, All, Night Stay, Instant, Motion, Maximum)” (sensorabsent; sensor tripped; sensor tampered; low battery); “Alarm”; and “NoiHub Connection” (broadband offline, etc.) (no security panelconnection). In addition to representing system state, the orb icons andtext summary elements of an embodiment generally represent system status4002 to include the following status: “All Quiet”; “Motion”; “Open”;“Open & Motion”.

Using various combinations of system state 4001 and status 4002, the orbicons of an embodiment indicate or represent numerous system states.

When the system state 4001 is “Disarmed” or “Subdisarmed”, the orb iconsof an embodiment indicate or represent status 4002 as follows: Disarmed(status: all quiet) 4010 (e.g., icon color is green); Disarmed (status:motion) 4011 (e.g., icon color is green); Disarmed, (number of sensorsopen) Sensor(s) Open (status: open) 4012 (e.g., icon color is green,bottom region for sensor number is yellow); Disarmed, (number of sensorsopen) Sensor(s) Open (status: open and motion) 4013 (e.g., icon color isgreen, bottom region for sensor number is yellow).

When the system state 4001 is “Armed (Doors and Windows, Stay, Away,All, Night Stay, Instant, Motion, Maximum)”, the orb icons of anembodiment indicate or represent status 4002 as follows: Armed Doors &Windows (status: all quiet) 4014 (e.g., icon color is red); Armed Doors& Windows (status: motion) 4015 (e.g., icon color is red); Armed Doors &Windows, (number of sensors open) Sensor(s) Open (status: open) 4016(e.g., icon color is red, bottom region for sensor number is yellow);Armed Doors & Windows, (number of sensors open) Sensor(s) Open (status:open and motion) 4017 (e.g., icon color is red, bottom region for sensornumber is yellow).

When the system state 4001 is “Disarmed”, or “Subdisarmed” (sensorabsent; sensor tripped; sensor tampered; low battery; uncleared alarm),the orb icons of an embodiment indicate or represent status 4002 asfollows: Disarmed, sensor problem (status: all quiet) 4018 (e.g., iconcolor is green, badge in top region with “!” symbol is red); Disarmed,sensor problem (status: motion) 4019 (e.g., icon color is green, badgein top region with “!” symbol is red); Disarmed, sensor problem (status:open) 4020 (e.g., icon color is green, badge in top region with “!”symbol is red, bottom region for sensor number is yellow); Disarmed,sensor problem (status: open and motion) 4021 (e.g., icon color isgreen, badge in top region with “!” symbol is red, bottom region forsensor number is yellow).

When the system state 4001 is “Armed (Doors and Windows, Stay, Away,All, Night Stay, Instant, Motion, Maximum)” (sensor absent; sensortripped; sensor tampered; low battery), the orb icons of an embodimentindicate or represent status 4002 as follows: Armed Doors & Windows,sensor problem (status: all quiet) 4022 (e.g., icon color is red, badgein top region with “!” symbol is red); Armed Doors & Windows, sensorproblem (status: motion) 4023 (e.g., icon color is red, badge in topregion with “!” symbol is red); Armed Doors & Windows, sensor problem(status: open) 4024 (e.g., icon color is red, badge in top region with“!” symbol is red, bottom region for sensor number is yellow); ArmedDoors & Windows, sensor problem (status: open & motion) 4025 (e.g., iconcolor is red, badge in top region with “!” symbol is red, bottom regionfor sensor number is yellow).

When the system state 4001 is “Alarm”, the orb icons of an embodimentindicate or represent status 4002 as follows: Armed Away/Stay, (alarmtype) ALARM 4026 (e.g., icon color is red).

When the system state 4001 is “No iHub Connection” (broadband offline,etc.) (no security panel connection), the orb icons of an embodimentindicate or represent status 4002 as follows: Status Unavailable 4027(e.g., icon color is grey).

When the client of an embodiment is a touchscreen, a mini orb ispresented at the bottom of the touch screen in all widgets and settingsscreens. The mini orb is green when the security panel is disarmed, andit is red when the security panel is armed, but is not so limited. Theform factor of the mini orb, and the text corresponding to the mini orb,is the same or similar to that described above as corresponding to theorb icon on the home screen.

The orb icons of an embodiment include motion indicators that animate toindicate motion detected by a corresponding sensor or detector.Furthermore, the orb icons of an embodiment show an animation during theexit delay when arming the security system and, additionally, indicate acountdown time showing the time remaining before the security system isfully armed. Moreover, selection of the orb of an embodiment causesadditional information (e.g., list of sensors, etc.) of the securitysystem and/or premise to be displayed.

The text summary display element of the SUI includes or displaysinformation including a direct description of the current state of thesecurity system to support the visual appearance of the orb icon. In anembodiment, two phrases are shown, including a first phrase for securitystate and a second phrase for sensor status (e.g., “Armed Stay. AllQuiet”), as described herein. FIG. 6 is a table of security state andthe corresponding sensor status displayed on the SUI, under anembodiment. The possible values for the text summary are (in priorityorder): Status Unavailable; if the security panel and control box areonline and there are no current alarms, the text summary section is acombination of one phrase from each of the security state 4030 and thesensor status 4032. The security state 4030 of an embodiment is selectedfrom among the following, but is not so limited: Armed Doors & Windows;Armed All; Armed Stay; Armed Away; Disarmed; Armed Maximum; Armed NightStay; Armed Stay Instant; Armed Away Instant; Armed Motion; Subdisarmed.The sensor status 4032 of an embodiment is selected from among thefollowing, but is not so limited: Uncleared Alarm; Sensor Tripped;Sensor Problem; Sensor(s) Bypassed; Motion; All Quiet; (number ofsensors open) Sensor(s) Open.

The display elements of the SUI also include security buttons. Thesecurity buttons are used to control or arm/disarm the security panel. Asingle arm button (e.g., button labeled “Arm”) can be used on the SUI ofa first client device type (e.g., Touchscreen, iPhone, etc.). Twodifferent buttons (e.g., buttons labeled “Arm Away/Arm Stay” or “ArmAll/Doors and Windows”) can be used on the SUI of a second client devicetype (e.g., web portal, mobile portal, etc.). In either embodiment, whenthe system is armed, the arm button (e.g., “Arm”, “Arm Stay” and “ArmAway”) label will change to a “Disarm” label. If the system is in theprocess of arming, the button is disabled.

The display elements of the SUI include system and device warnings, asdescribed above. The system and device warning are informationalwarnings that are not associated with specific sensors, and involve moredetail than can be displayed in the text summary display element. FIG. 7is a table of system state and the corresponding icons and warning textdisplayed as system warnings on the SUI, under an embodiment. Where anicon is displayed, an embodiment uses a red color for the icon, but itis not so limited. The system states/warnings of an embodiment include,but are not limited to, the following: primary connection is broadband,broadband is down, cellular is being used/using cellular connection;primary connection is broadband, broadband and cellular are down/nocellular connection; primary connection is broadband, broadband is down,no cellular backup installed/broadband connection unknown; primaryconnection is cellular, cellular is down/no cellular connection;security panel not connected to AC power/security panel AC power loss;security panel low battery/security panel low battery; security paneltampered/security panel tampered; sensor(s) bypassed/sensor bypassed.

The device warnings of an embodiment include, but are not limited to,the following: camera(s) offline; light(s) offline; thermostat(s)offline. The device and system warnings may be combined into one box, orindicated separately in respective regions or portions of the SUI,depending on a type of the client device (e.g., combined into one box ona web portal or a mobile portal, but indicated in separate boxes on aTouchscreen or iPhone® device).

The device and system warnings display element is cumulative (e.g.,built up in a list), but is not so limited. On the web and mobileportals the system and device warnings of an embodiment are combinedinto one area, but are not so limited. On the touchscreen device andmobile phone (e.g., iPhone), device warnings are indicated separately sothat, in an embodiment, the iPhone® tab bar and the touchscreen homescreen indicate device warnings with icon badges, and system warningsare placed on the sensors screen.

The list of all sensors includes, but is not limited to, door/windowsensors, motion detectors, smoke, flood, fire, glass break, etc. Thelist of all sensors of an embodiment does not include cameras or locks,or non-security related devices such as lights, thermostats, energy,water etc. The list of sensors is split into groups that, in anembodiment, include interesting sensors as a first group, and quietsensors as a second group. The interesting sensor group is positionedabove or sorted to the top portion of the sensor list and the quietsensors are sorted to the bottom portion of the sensor list. Any sensorthat is triggered (e.g. open, motion, etc.) is categorized as aninteresting sensor and placed in the interesting sensor group and list.Additionally, other sensor states such as tampered, tripped, absent,installing, low battery, or bypassed make a sensor “interesting”regardless of their state.

FIG. 8 is a table of sensor state/sort order and the corresponding icon,sensor name and status text of the SUI, under an embodiment. Generally,the list of interesting sensors is sorted according to the followingcategories: motion; open/tripped; tampered; low battery; offline;installing; bypassed. Sensors are sorted alphabetically by sensor namewithin each category or interest type when multiple interesting sensorshave the same state. The sensor state/sort order of an embodimentincludes, but is not limited to, the following: breached & any sensorstate (e.g., red icon) (interesting sensor); tripped (smoke, water, gas,freeze, etc.) (e.g., red icon) (interesting sensor); tampered (e.g., redicon) (interesting sensor); low battery (e.g., red icon) (interestingsensor); offline/AWOL (e.g., red icon) (interesting sensor); unknown (ifthe iHub or Security Panel is offline, all sensors have a grey diamondicon and “Unknown” for the status text) (e.g., grey icon) (interestingsensor); installing (e.g., grey icon) (interesting sensor); open (e.g.,yellow icon) (interesting sensor); motion (e.g., yellow icon)(interesting sensor); bypassed (e.g., yellow or green icon) (interestingsensor); okay, closed, no motion (e.g., green icon) (quiet sensor).

The interesting sensors are shown or displayed with an icon. FIG. 9shows icons of the interesting sensors, under an embodiment. A reddiamond bang icon represents tamper, offline, bypassed, installing,and/or battery. A yellow triangle icon represents open or triggered. Awavy lines icon represents motion. It is possible for an interestingsensor to have a green/closed icon (e.g., any quiet sensor that has beenbypassed).

Following the state icon and the sensor name an embodiment displaysstatus text. The status of an embodiment includes, but is not limitedto, the following: ALARM, (sensor state); tripped; tampered, (sensorstate); low battery, (sensor state); offline; unknown; installing;bypassed, (sensor state). If a sensor is offline or tampered, it willshow that text; otherwise the status text will show the tripped state:open, motion, tripped, etc. In addition, if a sensor is bypassed itsstate is “Bypassed, (sensor state)”. For example, a bypassed motionsensor that has recently detected motion would have the status: “Motion,bypassed”. If a sensor has a low battery its state does not change, butit still joins the interesting sensors group.

The quiet sensors include the remaining sensors that are not currentlyactive, and so are not categorized as interesting sensors. Quiet sensorstates of an embodiment include closed, no motion or otherwise nottripped or faulted. FIG. 10 shows the quiet sensor icon, under anembodiment. A green circle icon is a quiet sensor icon in an embodiment,and represents closed/no motion/okay/quiet. In addition to the stateicon and sensor name, each quiet sensor shows status text as follows: ifa door/window sensor is closed its state is “closed”; if a motion sensorhas not recently detected motion then its state is “no motion”; othersensors, such as a smoke detector, indicate “quiet” or “okay”. Quietsensors are listed alphabetically.

The SUI of an embodiment includes control icons for a Home ManagementMode (HMM). If the user deselects the “Set home management modesautomatically” setting via the web portal, then the Home Management Mode(HMM) screen will appear in the web and mobile Portals. FIG. 11 is anexample Home Management Mode (HMM) screen presented via the web portalSUI, under an embodiment. The HMM screen includes an orb icon andcorresponding text summary display elements, along with security buttonsthat control or arm/disarm the security panel. Furthermore, the HMMscreen includes sensor status information (e.g., “Door”, status is“open”, icon is yellow; “Basement Motion”, status is “motion”, icon isyellow; “Family Room North Motion”, status is “motion”, icon is yellow;“Water”, status is “okay”, icon is green).

FIG. 12 is an example Home Management Mode (HMM) screen presented viathe mobile portal SUI, under an embodiment. The HMM screen of the mobileportal includes an orb icon and corresponding text summary displayelements, along with security buttons that control or arm/disarm thesecurity panel.

The SUI of an embodiment is supported on numerous client types, forexample, mobile telephones (e.g., iPhone®, etc.), client access viamobile portal, client access via web portal, and touchscreen to name afew. All clients types supported in an embodiment have the same statusrelated sections, but their locations change slightly depending on theclient. The status related sections of an embodiment include thefollowing: orb; arm state/sensor summary; change mode; device summaryand system warnings; interesting sensors; and quiet sensors.

FIG. 13 is a block diagram of an iPhone® client device SUI, under anembodiment. The client interface of the iPhone®, as one example client,has the orb on the security page. The text summary is below the orb. Thesecurity button (e.g., arm, disarm, etc.) is below the text summary. Atab bar is presented at the bottom of the screen. The SUI of anembodiment represents device warnings by the icons in the bottomhorizontal tab bar. If a camera, light, lock, or thermostat is offlinethen a red circle will badge the corresponding icon in the tab bar. Thenumber of offline devices is shown in the badge. FIG. 14 is a firstexample iPhone® client device SUI, under an embodiment. In this firstexample screenshot, the security page indicates one camera is offline,as indicated by the “1” in a “circle” badge displayed corresponding tothe “camera” icon in the tab bar.

System warnings appear as a group in an area (e.g., yellow area) at thetop of the sensor status screen. This area at the top of the sensorstatus screen appears only when there is a device or system warning;otherwise, it is not presented. Multiple messages appear as a verticallist with one message on each line. The yellow bar will grow in lengthto fit additional messages. If there are no system warnings then theinteresting sensors group is at the top of the sensor status screen.Interesting sensors are presented below system warnings. Quiet sensorsare presented below interesting sensors. FIG. 15 is a second exampleiPhone® client device SUI, under an embodiment. In this second examplescreenshot, the sensor status page indicates at least one sensor isbypassed, as indicated by the “Sensor(s) bypassed” message displayed atthe top of the sensor status screen.

FIG. 16 is a block diagram of a mobile portal client device SUI, underan embodiment. The mobile portal of an embodiment comprises three (3)pages or screens presented to the client, including a summary page(“summary”), a security panel page (“security panel”), and a sensorstatus page (“sensors status”), but the embodiment is not so limited.The client interface of the mobile portal, as one example client, hasthe orb at the top of the summary page below the site name. The textsummary is below the orb. The security buttons (e.g., arm, disarm, etc.)(plural on mobile portal) are on the security panel page (accessible viathe “Security” link on the summary page). Device and system warnings arepresented in an area (e.g., yellow area) below the text summary; in anembodiment this area is presented only when device or system warningsare present. Interesting sensors presented are at the top of the sensorstatus page. Quiet sensors are presented below interesting sensors onthe sensor status page.

FIG. 17 is an example summary page or screen presented via the mobileportal SUI, under an embodiment. FIG. 18 is an example security panelpage or screen presented via the mobile portal SUI, under an embodiment.FIG. 19 is an example sensor status page or screen presented via themobile portal SUI, under an embodiment.

FIG. 20 is an example interface page or screen presented via the webportal SUI, under an embodiment. The client interface of the web portal,as one example client, has the orb in the center of the security widget.The text summary is below the orb. The security button (plurality in theweb portal) is adjacent to the orb's right side. System warnings arepresented in an area (e.g., yellow area) below the text summary; in anembodiment this area is presented only when device or system warningsare present. Multiple system warning messages are presented as avertical list with one message on each line, and the area dedicated tothe system warnings grows in length to accommodate additional messages.Interesting sensors span across the entire security widget below thetext summary. Quiet sensors span across the entire security widget belowinteresting sensors.

FIG. 21 is an example summary page or screen presented via thetouchscreen SUI, under an embodiment. The summary page of thetouchscreen, as one example, has the orb in the center of the securitybar. The text summary is split into sections or parts on each side ofthe orb. The security button is presented on the right side of thesecurity bar.

In addition to the orb, text summary, and security button, the summarypage also includes one or more icons that enable a transfer of contentto and from the remote network, as described in detail herein. Thetouchscreen integrates the content with access and control of thesecurity system. The content includes interactive content in the form ofinternet widgets. The summary page of an embodiment also comprises atleast one icon enabling communication and control of the premise devicescoupled to the subnetwork. The summary page also comprises one or moreicons enabling access to live video from a camera, wherein the camera isan Internet Protocol (IP) camera.

FIG. 22 is an example sensor status page or screen presented via thetouchscreen SUI, under an embodiment. The sensor status page of thetouchscreen, as one example, displays widget badges or iconsrepresenting device warnings. System warnings are at the top of thesensor status screen; in an embodiment this area is presented only whensystem warnings are present. Multiple system warning messages arepresented as a vertical list with one message on each line, and the areadedicated to the system warnings grows in length to accommodateadditional messages. Interesting sensors are below system warnings.Quiet sensors are below interesting sensors. The sensors screen alsoincludes the mini-orb which indicates the arm state with text and color.

The integrated security system of an embodiment includes a componentreferred to herein as “Home View” that provides end users an at-a-glancerepresentation of their home security status using the layout of theirhome. Like the System Icon or “orb” as described in detail herein, HomeView is intended to complement a set of common elements including, butnot limited to, the security text summary, arm/disarm button, systemwarnings, and sensor status list. These UI elements are in the primarydisplay of every iControl client application, and Home View adds to thatset of UI elements.

Home View can be an alternative to the System Icon, adding sensorlocation and information about other devices like lights, thermostats,cameras, locks, and energy devices, to name a few. Home View is anoptional view, and users who set up Home View are able to switch betweenthe System Icon view and Home View. Home View provides the user orinstaller a way to express the floor plans of their home, where thelayout of Home View is representational and, as such, is not meant to bea precise rendering of a home. The rendering of Home View can vary oneach device depending on screen size and display capabilities.

FIG. 23 is an example Home View display 4000, under an embodiment. Usingthis example, Home View 4000 expresses or represents with a display thefloor plan 4002 of a relatively large premise (e.g., home) or structure(e.g., 5 rooms wide and 5 rooms tall). Home View accommodatesmulti-story homes or structures (e.g., 4 stories). This mechanism canalso be used to express other parts of a property, such as outbuildings.Home View allows the user to see all devices 4010 present on a selectedfloor, and indications if other floors have interesting/active devices(such as an open door, or a light that is on).

Home View information defined on one client affects all clients. Inother words, if a change is made to the floor plans on one client, allclients display that change if they are using Home View. Home View isprovided on the iPhone, and is also supported on one or more clientscommon to all users (web portal and/or touch screen).

Home View of an embodiment includes an editing tool that supports basicsensors and common devices. Using the sensor state display of Home View,and while editing, the user can position each sensor device on eachfloor, and the sensor icon is displayed over each floor plan.

Under an embodiment and as further described below, basic device statesare represented by device and/or sensor state icons in Home View. FIG.24 shows a table of sensor state icons displayed on the Home View floorplan, under an embodiment. The sensor states displayed in an embodimentinclude, but are not limited to, the following: breached or alarmed,tripped, or tampered (e.g., red icon) (interesting sensor); low battery(e.g., red icon) (interesting sensor); offline/AWOL (e.g., red icon)(interesting sensor); unknown (if the iHub or Security Panel is offline,all sensors have a grey diamond icon and “Unknown” for the status text)(e.g., grey icon) (interesting sensor); installing (e.g., grey icon)(interesting sensor); open door/window (e.g., yellow icon) (interestingsensor); motion sensor active (e.g., yellow icon) (interesting sensor);okay, closed, no motion (e.g., green icon) (quiet sensor). The states ofeach sensor icon of an embodiment are updated periodically (typically15-30 seconds) to reflect their status.

A touch sensed anywhere in Home View navigates the UI to the sensor listavailable in System Icon view. The user can also touch any sensor iconin Home View and see a popup display showing the sensor name. The popupbox is presented above the sensor with a connector pointing to andindicating the sensor selected. If the sensor is at the top of thescreen, the popup box may appear below the sensor with a connectorpointing up to and indicating the selected sensor. The popup box alsoincludes a “more” button for navigating to detailed information aboutthat sensor (in this case, sensor history). An embodiment presentssensor icon, name, and status text, and the last event for that sensor,plus a navigation arrow e.g., (a blue circle on some UIs) the selectionof which switches screens to the sensor detail or history (same asclicking sensor name in each client).

Using the device state display of Home View, a set of device and/orsensor icons can be placed on each floor. FIG. 25 shows example sensorstatus and device icons of Home View, under an embodiment. The deviceicons include, but are not limited to, icons representing lights,thermostats, cameras, locks, and energy devices, to name a few. Each ofthe device icons change states in the same way they change in theirdevice list. These states include offline, installing, quiet, and activestates but are not so limited. In an embodiment, cameras do no indicatean active state with an icon change. When the user touches a deviceicon, the device name pops up or is displayed. The popup box includes a“more” button for navigating to more information about that device asfollows: camera icon (the popup box “more” button jumps to live videofor that camera; exiting live video returns to Home View); lights,thermostats, energy, locks icon (“more” button jumps to the detailscreen for controlling each device; the back buttons from those screensbehave as they always do).

Home View visually indicates changes in device state under anembodiment. Under one embodiment device icons represent an underlyingdevice component and its current state by modeling the device itself.For example (and as set forth in FIG. 25 ), an iconic image of a lockrepresents an actual lock device. As another example (and as set forthin FIG. 25 ), an iconic image of a lamp represents an actual lamp devicemonitored/controlled by the integrated security system. Home View maythen use the device icon itself to indicate change in state. Forexample, Home View may express an unlocked or open status of a lockdevice by replacing the symbol of a closed or engaged lock with a symbolclearly depicting a lock that is unlocked or disengaged. As anotherexample, Home View may indicate an inactive lamp device by replacing aniconic lamp representation in an “on” state (i.e., indicating emanationof light) with a darkened lamp representation (using a darkened lampshade) indicating an “off” status. In other words, change in appearanceof the device icon expresses a change in state of the underlying device.

Under another embodiment a generic sensor icon may be used to representa device and its operational status. For example, a user may use an editfeature of Home View (described in greater detail below) to place ageneric sensor icon on the Home View floor plan. When the user touchesthe icon on an iPhone client or mouses over the icon in a webapplication, the name/type of device appears above the icon (along withother relevant information and options as further described herein). Theicon itself then displays status by shifting to a state specific statusicon. As described above, Home View may use one of the status iconsdescribed in FIG. 24 as appropriate to the operational status of therepresented device but is not so limited.

Under another embodiment, Home View may indicate a change in state ofthe device by simply replacing the device icon with a status icon. Forexample, a lock device may be offline at which time the Home View wouldreplace the lock icon representation with a status icon representationthat indicates an offline status. The offline status icon may correspondto the offline status symbol set forth in FIG. 24 but is not so limited.

Under another embodiment, Home View may visually superimpose or visuallyannotate a device icon with status representations. As an example, HomeView may visually annotate a lock device icon with a status icon toindicate its current operational status. The Home View may use thestatus icons described in FIG. 24 to visually append status informationto device representations but is not so limited. Under an embodiment,the Home View may use smaller representations of such icons to serve asstatus badges on a portion of the device icons. The Home View may alsosuperimpose a partially transparent status icon as a palimpsest layerover the device icon or alternatively integrate a partially transparentstatus icon into the device icon as a watermark representation. HomeView may use one of the status icons described in FIG. 24 as appropriateto the operational status of the represented device but is not solimited.

Under yet another embodiment, Home View may use any combination and/ormanipulation of status/device icons to represent operational status ofsystem components.

If more than one floor has been defined in Layout mode of Home View,thumbnails on a portion of the display indicate that there are floorsabove or below the current one, and a means provided to switch floors.FIG. 26 shows a Home View display 4100 that includes indicators4101/4102 for multiple floors, under an embodiment. In this example, twoicons are presented to indicate a first (lower) floor 4101 and a second(upper) floor 4102. The currently-displayed floor 4101 (e.g., first(lower) floor) is outlined in white or otherwise highlighted. Thelast-viewed floor will be remembered across sessions.

The display of indicators for multiple floors through a mobile portalincludes numbered links on a portion of the display (e.g., right),starting from “1”. The currently-displayed floor is shown as bold, andnot a link, as in:

-   -   Floor: 1 2 3

Like the System Icon, Home View indicates the overall system state byusing background color. For accessibility, this may also be presentedusing corresponding text located adjacent to the icon. FIG. 27 shows thesystem states along with the corresponding Home View display and systemor orb icon, under an embodiment. Across all clients, system state isindicated using a representative color. The disarmed or subdisarmedsystem state is displayed in Home View using a green background or greenborder 4202 on the floor plan. The armed (any type) system state isdisplayed in Home View using a red background or red border 4204 on thefloor plan. The alarm system state is displayed in Home View using a redbackground (with or without black diagonal stripes) 4206 on the floorplan. The offline (iHub or panel) system state is displayed in Home Viewusing a grey background 4208 on the floor plan.

The System Icon of some client device UIs (e.g., the iPhone, the TouchScreen) also includes a warning badge to indicate that there arewarnings to see in the sensor list. In Home View, a general warningindicator 4302 is shown in a region (e.g., on one side) of the Home Viewfloor display. FIG. 28 shows a Home View floor display (disarmed 4202)that includes a warning indicator 4302, under an embodiment. The HomeView display and warning indicator correspond to the system icon or“orb” set forth in the upper left corner of FIG. 28 .

The use of Home View as a user interface includes Summary Text asdescribed in detail herein, and the Summary Text provides definitiveinformation on the current arm state, and a summary of any sensorissues. Additionally, the system arm/disarm buttons are displayedseparately. FIG. 29 shows an example of the Home View 4402 using theiPhone security tab, under an embodiment. System state information 4404is displayed (“Disarmed. 1 Sensor Open”), and an “Arm” button 4406 isdisplayed by which a user arms the system.

Home View is an alternative to the System Icon, as described herein, andis configured via site settings. Each application retains the user'spreferred mode across sessions. FIG. 30 shows an example screen for siteSettings 4500, under an embodiment. The Settings screen 4500 includes alist of sites 4502 that can be selected, along with a Sign Out button4504. The Settings screen 4500 also includes a Security Tab Optionsbutton 4506. Selection of the Security Tab Options button 4506 displaysthe Security Tab Options screen 4600.

FIG. 31 shows an example screen for Security Tab Options 4600, under anembodiment. The Security Tab Options screen 4600 displays a list ofoptions 4602 to select what the security tab displays (i.e., the SystemIcon display or the Home View display), along with an Edit Home Viewbutton 4604. When the user first attempts to switch to Home View fromthe Security Tab Options screen 4600 the following modal dialog isdisplayed: “Home View must be set up before use.” This dialog includesbut is not limited to the following two buttons: “Set Up Now” and“Cancel”.

Any time the user wants to alter their Home View floor plans or devicepositions, they can choose Settings 4500, then select the Security TabOptions button 4506, then the Edit Home View button 4604. If a devicehas been deleted, then the Home View display code removes it from thedevice settings table. If a device has been installed or added to thesystem, it does not automatically appear in Home View, but it will beavailable in Edit Home View mode, ready to be placed on a floor.

The Home View mode of an embodiment includes an editor or Edit Mode. Onthe Settings screen 4500, the user can select Security Tab Options 4506,then Edit Home View 4604, as described above. This puts the user in Editmode, where they can make changes to device positions, floor plans, andadd/remove floors, for example. When editing is complete, selection of a“Done” button on the screen returns a user to the Security Tab Optionsscreen 4600. If the user has made changes, then a dialog slides up thatincludes buttons for “Save Changes”, “Don't Save”, and “Cancel”. Oncesaved, Home View data is saved on the iHub/iServer with other sitesettings, and can appear in any client that has Home View enabled fordisplay.

When the user first enters Edit mode, the user selects a basic floorplan which defines the perimeter shape of each floor of the premise.FIG. 32 shows an example “Add Floor” screen for use in selecting a floorplan, under an embodiment. Numerous floor plan selections are presentedin a region of the screen labeled “Select a floor plan” 4702, and thefloor plan selections 4702 of an embodiment comprise, but are notlimited to, the following: square; horizontal; vertical; four differentL-shapes; four different U-shapes; four different zigzag shapes. Thetitle bar of the “Add Floor” screen 4700 includes a Cancel button 4704.At the point when there are no floors, there are no other buttons.

Upon selection of a basic floor plan, the editor is displayed. FIG. 33shows an “Edit Home View” screen 4800 of the editor, under anembodiment. The title bar includes an add floor button [+] 4802. In thisexample only one floor is defined, so there is no delete button (cannotdelete the last floor). In addition to adding and deleting floors, theeditor of an embodiment displays selection buttons 4810-4814 for threeediting modes: Devices mode 4810 (used for placing devices on eachfloor); Walls mode 4812 (used for adding or changing walls); Erase mode4814 (used for deleting walls). If the default floor plan matches theuser's home, then the user has only to position devices on that floor.However, if the user wishes to modify a floor plan or define interiorsthen the Walls Mode and Erase mode are used to make changes.

Devices are represented by icons in the editor, and the icons can bepositioned by dragging to the appropriate location on the floor plan4804. Below the displayed floor 4804 is a dock area 4806 that includesall devices displayed in rows. The user can drag a device to any tile onthe floor 4804 that does not already contain a device icon. Devices canalso be dragged back off the floor 4804 and onto the dock 4806. Toidentify a device the user can tap a device icon or start dragging andthe name will appear above the device icon. FIG. 34 shows an example ofdragging a device icon during which a name of the device 4900 (“FrontDoor”) is displayed, under an embodiment. Devices are not required to beplaced on floors, and any devices left in the dock 4806 are ignored whenHome View is displayed. These can be added to any floor at a subsequenttime. Newly installed devices are also left on the dock 4806, ready tobe placed when editing.

The dock 4806 has a grid of tiles, similar to the floor plans. The usercan move devices around on that grid. Upon exiting the editor and thenreturning, the dock is drawn in ordered rows. Devices of an embodimentare placed every-other-tile, up to 11 devices per row and up to 3 rowsfor a total of up to 33 devices on screen, but are not so limited. Ifthe site has more than 33 devices in the dock, they are not shown untilsome devices are moved onto the floor, so that the dock condenses aftereach device is placed on a floor.

The selected floor plan provides a basic perimeter for the floor. If theuser wishes to change the default perimeter walls or define interiorwalls, the user can switch to Walls mode. The user can tap any tile tocustomize that tile, and tapping a tile cycles the tile through twelvedifferent tile shapes. Tile cycles start with the best-fit tile based oncontext, then cycle through all possible tile shapes in best-fit order.For example, if the user taps a blank tile with a horizontal line to theright and a vertical line below it, then the first tile drawn will be acorner tile that connects those lines, then a tile that connects oneline, then the other line, etc.

For example, a typical task is to draw an interior wall. Each tileshould require only one tap to draw as a user progresses across tiles ofthe floor plan. FIG. 35 is an example of a U-shaped floor plan 5000customized by changing interior tiles to define walls 5002, under anembodiment.

The editor of an embodiment includes a Walls mode and an Erase mode, asdescribed above. In the Walls mode and the Erase mode the device iconsare hidden. Erase mode is used to change wall tiles into blank tiles, toremove mistakes, and/or begin to move a wall. For example, a userwanting to narrow a rectangular floor plan by moving an entire wallinward first switches to Erase mode and taps every tile of the verticalwall they wish to move, and then switches to Walls mode and taps everytile where they wish a wall to be placed.

An embodiment may adopt an alternative floor plan editing scheme in theform of a commercial diagramming tool. The alternative approach replacesthe tile based diagramming described above with a vector based graphicsapproach. A user may choose design primitives to establish andsubsequently manipulate (via touch/drag interactions or keyboard/mouseoperations) basic floor plan shapes and representations. Such approachmay incorporate a “free hand” ability to trace lines or other floor planelements (via touch/drag interactions or keyboard/mouse operations).

While editing tiles or positioning sensors, more precision may be neededin which case the user can toggle the zoom level of the editor (includesthe dock) in any edit mode. To zoom to 300%, for example, the user tapsthe + magnifying glass 5004, and to return to 100% zoom, the user tapsthe − magnifying glass 5102. If there are multiple floors, tapping afloor thumbnail returns to 100% zoom. Once zoomed, the user scrollsaround the floor by a dragging operation. FIG. 36 shows an example inwhich the zoom level is increased and dragging has been used to focus ona sensor location 5100, under an embodiment. When zoomed in, if the usertouches and drags a device, the device moves and not the floor. If theuser taps and drags a tile, the floor scrolls around and the tile is notaltered.

Home View of an embodiment supports up to four (4) floors but is not solimited. These floors can also be used for other physical spaces, suchas outbuildings or garages for example, so floor numbering is generallyavoided. To define a new floor in Edit mode, the user touches a + button4802 at the top of the screen and the Add Floor page appears. FIG. 37 isan example “Add Floor” page 5200, under an embodiment. If at least onefloor has previously been defined, a new control appears to help addthis new floor above (“Add Above” 5202) or below (“Add Below” 5204) thecurrent floor. The default option adds the new floor above (“Add Above”)the current floor. By selecting a floor in Edit mode, touching +, andchanging this control in the Add Floor page, the user can add basements,insert floors etc.

When more than one floor is defined in Home View, some differencesappear on the Edit Home View screen. Among the changes, a column offloor thumbnails appears on the right portion of the screen. Thecurrently selected floor thumbnail is highlighted, and the user can tapany floor to switch to that floor. For example, the user can move adevice to the dock, switch floors by touching the other floor thumbnail,then drag the device onto the new floor. FIG. 38 is an example Edit HomeView screen 5300 showing the floor thumbnails 5302/5304 for use inselecting a floor, under an embodiment.

An additional change displayed on the Edit Home View screen includes thedisplay of a delete floor button [−] in the title bar of the editor, tothe right of the add floor button [+]. If more than one floor isdefined, the user selects the [−] button to delete the current floor.The user is prompted with a warning with the options to Delete Floor orCancel 5404. FIG. 39 shows the Edit Home View screen 5400 with a deletefloor selector 5402, under an embodiment.

Selection of the Done button on the Edit Home View screen allows theuser to exit the editor. If upon selecting the Done button the user hasmade changes to the floors or device locations, the user is prompted tosave the changes before exiting back to the Settings screen. FIG. 40 isan example Edit Home View screen 5500 displaying options to “Save” 5502and “Don't Save” 5504 changes following selection of the Done button,under an embodiment.

For each premise, Home View allows users to define the floors of theirhome and the locations of all devices on those floors using the EditHome View layout editor described above. The output of the layout editorincludes two strings that are stored in site preferences on the server.All client applications share this static definition of the site layout,and locally combine it with the current state of the sensors and panelto produce a graphical view.

Home View is presented in an embodiment using tiles, and allows a userto define up to a pre-specified number of floors (e.g., four floors,etc.), but is not so limited. Each floor in Home View is presented as alayout of tiles in two layers or structures. A first layer, or bottomlayer, is a static layout of a single floor (e.g., 19 tiles by 19 tiles,etc.). FIG. 41 is an example of the floor grid data, under anembodiment. A second layer, or top layer, is a set of sensor/deviceicons (states changing) placed or overlaid over the grid (first layer).FIG. 42 is an example sensor hash table for a single-floor site, underan embodiment.

The server (e.g., iServer) of an embodiment stores the two structures intwo variables in site preferences, but the embodiment is not so limited.A first variable comprises a series of floor layouts corresponding tothe number of floors. Each floor layout is a floor grid represented by asingle string of characters (e.g., 19×19 or 361 ASCII characters), withone character corresponding to each tile as described above.

The homeViewLayouts preference strings represents between 1 and 4 tilegrids. Each tile grid is 19 tiles by 19 tiles for a total of 361 tiles.The grids comprise odd numbers to support centering of walls. The first361 tiles represent the first floor of the premise. If there aremultiple floors, the next 361 tiles represent the second floor of thepremise. Therefore, homeViewLayouts length is 361 characters (premisehaving one floor), 722 characters (premise having two floors), 1083characters (premise having three floors), or 1444 characters (premisehaving four floors). FIG. 43 shows an example homeViewLayouts string,under an embodiment.

A second variable comprises a hash table mapping specific tiles tosensors, separated by commas, and every sensor is represented. AhomeViewDevice preference string represents such information andcomprises key,value pairs separated by commas. As examplehomeViewDevices character string is as follows:

-   -   homeViewDevices=“3,zone2,74,zone5,88,zone1,129,zone2,166,        cameraFront Door Cam,200,lightUpstairs Light        2,226,thermoUpstairs”.

The key of the key,value pair is an integer representing the absoluteoffset into the homeViewLayouts array. The value of the key,value pairrepresents a way to precisely identify the device. For sensors, thisvalue is “zone” followed by the zone ID. For example, if the front door(zone id 7) is on the third tile over, then the key value pair is2,zone7 (e.g., zero-based offset).

Each tile set includes twelve basic shapes. The shapes of an embodimentinclude, but are not limited to the following: empty; horizontal wall;vertical wall; top left corner; top right corner; bottom left corner;bottom right corner; T-shape down; T-shape right; T-shape up; T-shapeleft; 4 corner shape. FIG. 44 shows the twelve shapes of a tile set,under an embodiment. Wall lines are centered within each tile to ensurealignment. The user draws the floor(s) of their premise using theshapes, and the set of tile shapes is used while editing (generallyblue, like blueprints), and for two of the rendered states of thesecurity system: when alarmed (red and black striped) and when offline(gray tiles).

As stated above, the user defines the walls of each floor of their homeusing twelve basic tile shapes. However, when a floor is rendered, thebuilding exteriors should be readily distinguished from the interiors.For rendering Home View in armed and disarmed states, algorithmsdetermine the interior of the home and compute which tiles aretransparent and which tiles are filled. For perimeter walls, thealgorithm clears the exterior side but not the interior side. A largerset of tiles is used to handle all possible transparent/filled tilerenderings. FIG. 45 shows the tile shapes and corresponding fill optionsfor rendered tiles, under an embodiment.

As stated above, the user defines the walls of each floor of their homeusing twelve basic tile shapes. However, when a floor is rendered, thebuilding exteriors should be readily distinguished from the interiors.This achieved when the editor is exited and tiles exterior to eachbuilding are replaced with transparent tiles. Similarly, tiles withwalls facing the exterior are replaced with tiles where the exteriorportions are transparent.

FIG. 46 is an example tile rendering for a room of a premise, under anembodiment. In this example, there are two perimeter versions of thetop-right corner tile “t”, and one perimeter version is filled on thebottom right (tile “u”), and one perimeter version is filled on the topleft (tile “U”).

A description follows for operation of the algorithm for determining aninterior and an exterior. The algorithms generate a list of all tiles onthe edge of each floor that are empty (top row, bottom row, left column,right column, up to 19+19+2*17=72 tiles per floor). With each tile, afunction is called to clear the tile. In that function, the empty tileis changed to an empty exterior tile (for example, “e” changes to “E”).The algorithm then examines the four tiles on each side (top, right,bottom, left) of the current tile and, if they are non-empty, replacesthem with tiles where the side facing the current tile is transparent.The algorithm then examines the four tiles diagonal to this exteriortile and, if they are non-empty and have a corner (T shapes, plus shape,corners), replaces them with tiles where the corner facing the currenttile is transparent. A list is generated comprising any of the fourtiles on each side (top, right, bottom, left) of the current tile thatare empty. With each empty tile, a recursive function is called and theprocess repeats as described above.

In order to avoid stepping into “doors”, the algorithm does not call therecursive function in response to empty tiles if there are wall edgestouching the current tile. For example, the process only recurses downto an empty tile if the tiles to the right and left are not horizontaltiles (or similar) touching the current tile. This works for doors oneand two tiles wide; wider openings get filled.

The fully computed floor definition is stored in the gateway (e.g.,iHub) and/or server (e.g., iServer) but is not so limited. If the HomeView editor is used, these computed tiles can be converted back to thetwelve-tile set while editing. The Home View data output from Edit modeis checked to ensure integrity of parameters, for example: the number oftiles (and number of floors) is correct; the tile data only includesvalid tile characters; all sensors and devices still exist. At the timeHome View is rendered, the same checks are again performed to verifydata integrity. If any checks fail, the user is presented a dialog, andthe preference returns to the System Icon (the “orb”). Essentially thefeature is turned off for display, but the data is still there untiledited. If the user tries to edit home view and the data is corrupted,they are given the option to reset the data and start over.

An alternative embodiment of Home View also provides methods forgenerating and presenting floor plans and icons representing sensorsoverlaid on a floor plan for a home, thereby enabling users to quicklysee the state of each sensor (such as open doors, status of lights andthermostats, etc.), and click on any sensor to get more informationabout that sensor. As described in detail herein, FIG. 24 shows a tableof sensor state icons displayed on the Home View floor plan, and FIG. 25shows example sensor status and device icons of Home View, under anembodiment. The device icons include, but are not limited to, iconsrepresenting lights, thermostats, cameras, locks, and energy devices, toname a few. Each of the device icons change states in the same way theychange in their device list. These states include offline, installing,quiet, and active states but are not so limited. The sensor statesdisplayed in an embodiment include, but are not limited to, thefollowing: breached or alarmed, tripped, or tampered (e.g., red icon)(interesting sensor); low battery (e.g., red icon) (interesting sensor);offline/AWOL (e.g., red icon) (interesting sensor); unknown (if the iHubor Security Panel is offline, all sensors have a grey diamond icon and“Unknown” for the status text) (e.g., grey icon) (interesting sensor);installing (e.g., grey icon) (interesting sensor); open door/window(e.g., yellow icon) (interesting sensor); motion sensor active (e.g.,yellow icon) (interesting sensor); okay, closed, no motion (e.g., greenicon) (quiet sensor). The states of each sensor icon of an embodimentare updated periodically (typically 15-30 seconds) to reflect theirstatus.

A touch sensed anywhere in Home View navigates the user interface to thesensor list available in the System Icon view. The sensor icons of anembodiment update periodically (e.g., frequently) to reflect theircurrent status (e.g., an open window). The sensor icon also representsthe “health” of that sensor (offline, low battery etc.). A user canhover over (in desktop web browser) or tap (tablet/touch device) anysensor icon and see a popup display showing the name, state, and thelast event for that sensor. FIG. 47 is an example popup display inresponse to hovering near/adjacent a sensor icon (e.g., “Garage”sensor), under an embodiment. If the device is at the very top of thescreen, the popup box may appear below the sensor. Alternatively, if thedevice is on the edge of the screen the popup box may be pushed inwardor displayed in another portion of the interface. Clicking (desktop) ordouble-tapping (tablets) in regions of the display causes the system tonavigate to sensor history. When the interface is displayed on aniPhone, for example, the popup box may also have a blue “more” buttonfor that same navigation.

If more than one floor has been defined in Layout mode of Home View, thedisplay includes thumbnails on a portion of the display that indicatethe existence of floors above or below the current one, and a process toswitch floors. FIG. 48 shows a Home View display that includes a floorplan display 4800 of a selected floor along with indicators 4801/4802for multiple floors, under an embodiment. In this example, two icons arepresented to indicate a first (lower) floor 4801 and a second (upper)floor 4802. Alternatively, other notations (e.g., dots, etc.) can beused to indicate multiple floors. The currently-displayed floor 4801(e.g., first (lower) floor) is highlighted. The last-viewed floor willbe remembered across sessions. When accessing Home View via a mobileportal, the display of indicators for multiple floors through the mobileportal includes numbered links on a portion of the display (e.g.,right), starting from “1”. The currently-displayed floor is shown asbold, and not a link, for example:

-   -   Floor: 1 2 3

The use of Home View as a user interface includes a system icon orSummary Text that provides definitive information on the current armstate, and a summary of any sensor issues. Additionally, the systemarm/disarm buttons are displayed separately. FIG. 49 shows an example ofthe Home View user interface displayed via a mobile device (e.g.,iPhone), under an embodiment. The user interface 4900 includes a floorplan display 4901 of a selected floor along with indicators 4902 forselecting among corresponding multiple floors of a building. Systemstate information is displayed 4903 (“Disarmed. All Quiet”), and an“Arm” button 4904 is displayed by which a user controls arming of thesystem. A toolbar 4905 is included by which a user selects a device type(e.g., security, cameras, lights, thermostats, etc.) for which statusand control information is available via Home View.

Home View is configured via site settings as described in detail herein.Each application retains or remembers the user's preferred mode acrosssessions. FIG. 50 shows an example of a Settings page of Home View,under an embodiment. The Settings page includes a Sites list, a “HomeView” button 5001, and a corresponding On/Off switch 5002. For siteowners, there is also a “Set Up Home View” button (not shown), theselection of which directs the system to the editor. Once Home View isdefined by a user, the interface presents the “Set Up Home View” buttonas an “Edit Home View” button 5003. In the web portal of an embodiment,Home View can be enabled and edited using a Customize link on theSummary tab. Users can check the box to show Home View, and site ownerswill have an Edit button.

Any time the user wants to alter their Home View floor plans or devicepositions, they can choose Settings and then select the Edit Home Viewbutton. If a device has been deleted, then the Home View display coderemoves it from the device settings table. If a device has beeninstalled or added to the system, it does not automatically appear inHome View, but it will be available in Edit Home View mode, ready to beplaced on a floor.

The Home View mode of an embodiment includes an editor or Edit Mode, asdescribed in detail herein. On the Settings screen, the user can selectthe Edit Home View button, as described above. This puts the user inEdit mode, where they can make changes to device positions, floor plans,labels, and add/remove floors, for example. When editing is complete,selection of a “Done” button on the screen returns a user to theSecurity Tab Options screen. If the user has made changes, then a dialogslides up that includes buttons for “Save Changes”, “Don't Save”, and“Cancel”. Once saved, Home View data is saved on the iHub/iServer withother site settings, and can appear in any client that has Home Viewenabled for display.

When the user first enters Edit mode, the user selects a basic floorplan that defines the perimeter shape of each floor of the premises.FIG. 51 shows an example “Home View Setup” editor page 5100 for use inselecting a floor plan, under an embodiment. Numerous floor planselections 5102 are presented in a region of the screen labeled “Selecta floor plan” 5102, and the floor plan selections of an embodimentcomprise, but are not limited to, the following: square; horizontal;vertical; numerous different L-shapes; numerous different U-shapes;numerous different zigzag shapes. The title bar 5103 is labeled “HomeView Setup” and includes a Back button 5104.

Upon selection of a basic floor plan, the selected floor plan isdisplayed. FIG. 52 shows a “Home View Setup” editor screen 5200 with aselected floor plan 5201, under an embodiment. The editor screen 5200displays a selected floor plan 5201, and includes a device dock 5202, ordock 5202, that includes devices 5203 as represented by icons. Theeditor 5200 includes an “Options” 5204 icon, the selection of whichpresents editing options. For example, FIG. 59 shows a Home View Setuppage 5900 with options displayed, under an embodiment. The editor 5200includes numerous editing operations including, but not limited to,positioning devices (dragging device icons from the dock and placingdevices on the floor), editing walls (adding new horizontal or verticalwalls, or deleting existing walls), and adding or editing labels(changing or deleting room labels). If the default floor plan matchesthe user's home, then the user has only to position devices on thatfloor plan. Optionally, the user can add labels. If the user wishes tomodify a floor plan or define interiors, however, then walls can bedrawn or erased.

Devices are represented by icons that are presented in a device icondock 5202 of the interface. The interface includes a dock area thatincludes device icons displayed in rows. Device icons are positioned onthe floor plan by dragging them from the dock to the appropriatelocation on the floor plan. To identify a device the user can tap adevice icon or start dragging the device and the name will appear abovethe device icon. Devices can also be dragged back off the floor and intothe dock. Furthermore, labels can be added to devices of the home (e.g.,front door 5301). FIG. 53 shows an example editor screen 5300 for whicha label 5301 with a name of the device (“Front Door”) is displayed,under an embodiment.

There is no requirement under an embodiment for devices to be placed onfloors, and any device left in the dock is ignored when Home View isdisplayed. The devices remaining in the dock can be added to any floorof a floor plan at a subsequent time. Newly installed devices are alsoleft on the dock, ready to be placed when editing. The dock of anembodiment is rendered in ordered rows, and the dock can be scrolledvertically to access all devices in the dock.

The selected floor plan of Home View provides a basic perimeter for thefloor, but is not so limited. A user wishing to draw new perimeter wallsor define interior walls drags across the grid lines to create newwalls. The user deletes walls in much the same way by dragging along thegridline over an existing wall. The process of erasing old walls thendrawing new ones can be used to “move” a wall but the embodiment is notso limited. For example, the process of narrowing a rectangular floorplan by moving an entire wall inward includes dragging over the verticalwall that is to be moved and then dragging on the new gridline where thewall is to be placed. FIG. 54 shows a Home View Setup page 5400 with aselected floor plan 5201 that has been edited to add numerous interiorwalls 5401, under an embodiment.

A user can edit labels on any location of a floor plan, where editingincludes adding, editing, and deleting labels. FIG. 55 shows a Home ViewSetup page with a label editing prompt 5501, under an embodiment. To adda new label, the user selects the option to add a room label and thentouches a location for that label. In response the interface presents alabel editing prompt 5501 for the label text. In order to edit anexisting label, the user taps that location and the same label editingprompt 5501 is presented for use in editing the label. To delete a labelthe user clears the text.

The floor plan editing of an embodiment includes zoom editing in orderto offer increased precision when editing. FIG. 56 shows a Home ViewSetup page 5600 in a zoomed editing mode to zoom on one room 5601 in abuilding, under an embodiment. The user edits in a zoomed mode bytapping a magnifying glass icon 5206 displayed on Home View Setup. Whenusing zoom editing, the magnifying glass icon 5206 of the Home ViewSetup page is replaced with a floor plan icon 5602 displaying the entirefloor plan with an overlay 5603 showing the region of the floor plan onwhich the user has zoomed. Once zoomed, the user scrolls around thefloor by dragging the view rectangle in the zoom thumbnail area. Tappingthe zoom thumbnail area returns the display to full zoom. When zoomediting, the touching and dragging of a device results in the devicebeing moved instead of the floor. When the user draws a wall and dragsthe wall, the editor scrolls the floor automatically.

Home View of an embodiment supports the addition of multiple floors, andthese floors can also be used for other physical spaces (e.g.,outbuildings, garages, etc.). FIG. 57 shows a Home View Setup page foradding at least one floor to a floor plan, under an embodiment. In orderto define a new floor in Edit mode, the user touches the Options button5204 at the top of the Home View Setup page and chooses Add Floor Above(e.g., FIG. 59 , element 5902). In response the Add Floor page 5700appears. In addition to the predefined floor plans, the current userfloor is also available for copying to a new floor. The Add Floor page5702 presents a prompt 5703 to select a floor plan along with numerousfloor plans 5704 available for selection.

The Home View editor supports editing with multiple floors. FIG. 58shows a Home View Setup page 5800 with editing for multiple floors,under an embodiment. When more than one floor is defined, the editor hasa few changes. For example, a column of floor thumbnails 5802 appears ina portion of the interface, and the currently selected floor thumbnail5801 is highlighted. At any time, the user can tap any floor to switchto that floor. As another example, a Remove Floor option is available inthe Options menu (see FIG. 59 , element 5902).

The Home View editor enables the setting of a default floor whenmultiple floors are included. Generally, the first floor is drawn firston any client. However, if multiple floors are included and the bottomfloor is not the default (e.g., a basement is included), Home Viewenables changing of this default. The default floor is changed, forexample, by tapping the icon for the second floor and then choosing theoption “Set As Default Floor” (see FIG. 59 , element 5902).

The Home View editor supports the moving of devices between floors whenmultiple floors are included. At any time, the user can move a device tothe dock, switch floors by touching the floor thumbnail corresponding tothe desired floor, then drag the device onto the new floor.

The Home View editor of an embodiment includes auto-fill interiors. Bydefault, the interiors of each floor of an embodiment are “filled” tolook different from the exteriors, and the interior walls are lessprominent than the exterior walls. The auto-fill interiors can beselectively enabled.

The Home View editor is exited by tapping a “Done” button 5204. Ifchanges have been introduced to the floors, device locations, or labelsduring an editing session, the editor prompts the user to save thechanges before exiting back to the Settings screen. FIG. 60 shows a HomeView Setup page 6000 with editor exit option prompts 6001 displayed,under an embodiment.

Home View of an embodiment includes or couples to a common data model.For each site, the site owner can use the Edit Home View layout editorto define the floors of the home, label the rooms of the home, andindicate the locations of the devices in the home. FIG. 61 is an examplefloor plan, under an embodiment. The output of the layout editor of anembodiment is represented using compact ASCII strings stored in sitepreferences on the server, but is not so limited. This storage schemeuses a virtual grid, and stores simple vector and x,y locations on thatgrid. For example, given a single-story home, the data describes thevisual components as follows: the lighter-shade interior tile areas aredescribed as two large rectangles; the stronger, exterior walls aredescribed as four horizontal and three vertical vectors; the lighterinterior walls are described as one horizontal and one vertical vector;the two device icons are each described with an x,y coordinate plusdevice identifier; the two room labels are each described with an x,ycoordinate plus the text.

This static ASCII data model of the home is stored by the editor so thatclient applications can fetch this static data model and combine itlocally with the current state of their devices to render a graphicalview. The only thing that subsequently changes are the device icons asusers take actions that affect the status of devices (e.g., open doors,turn on lights, etc.).

The data model strings are stored in three variables in site preferenceson the server. The three variables include homeview/floors,homeview/devices, and homeview/labels. The variable homeview/floorsspecifies where the walls should be drawn for each floor, and whetherinterior floor space should be filled. The variable homeview/floorsincludes a single floor, or multiple floors (separated in the data bysemicolons). If multiple floors are included, a default floor can beindicated so apps will display the default floor first.

The variable homeview/devices includes a list of floor locations anddevice IDs to draw on those locations. For multi-floor homes, per-floordata is separated by semicolons, but is not so limited. The list offloor locations and device IDs may be a subset of devices (the datamodel does not include information about devices that have not beenplaced on a floor).

The variable homeview/labels includes a list of locations, and textlabels to draw centered on those locations. For multi-floor homes thedata per floor is separated by semicolons.

Home View of an embodiment includes a compact method for storing numberswherein, throughout this model, numbers such as x,y coordinates andvector lengths are compactly represented using an ASCII-offset modelstarting with the lowercase alphabet (plus a few characters that followz in ASCII for >26), as follows:

-   -   a=0, b=1, c=2, . . . , x=23, y=24, z=25, {=26, |=27,}=28        The use of this model enables specification of any (x,y)        coordinate using two characters. For example, a horizontal line        drawn from x,y position 2,5 with a length of 20 (2,5,20) can be        represented by storing the “2” as “c”, storing “5” as “f”, and        storing 20 as t, compactly storing the line as “cft”.

The homeview/floors variable includes specific data elements, but theembodiments are not so limited. The data elements of an embodimentinclude the following: [max # of tiles across] [optional flag: don'tautofill interiors]; [floorplan data for 1st floor] [; floorplan datafor 2nd floor] [; 3rd floor] [; 4th floor] [; 5th floor].

The data element “max # of tiles across” is saved as 28 by default. Theresult is that the user can draw a floor plan using up to 28 wallshorizontally (29 walls vertically), containing 28 “tiles,” whichsupports a house with up to five rooms across.

The data element optional flag to prevent autofill interiors, whenincluded, instructs the Home View editor to never fill any floorinteriors when exporting the floor data. While the data may not includeany interior tiles, depending on how the walls were drawn, but this flagprevents any interior tiles from being computed by the editor.

The data element “semicolon” separates the general settings from thefirst floor data.

The data element “floorplan data for a single floor” includes anoptional flag plus a number of blocks of text representing vectors todraw, each block separated by spaces. The first character of each blockindicates the type of vector to draw, and the characters that followrepresent the vectors. When a floor should be shown first, the flag“default” is added before the vector data for that floor. Generally, thefirst floor is the default, so in that case (or in a single-floor house)this flag is not needed. The blocks of text representing the vectorsinclude but are not limited to an H block, V block, h block, v block,and t block.

The H block, when there are horizontal exterior walls to draw, startswith a capital H, followed by three characters for each horizontal wallto draw (startX, startY, length). For example, a 15-tile wall drawn fromthe top corner is represented as H(0,0,15), which is compactlyrepresented as Haap. A second horizontal wall drawn elsewhere appendsanother block of three coordinates. So Haap might become Haappph ifthere are two horizontal exterior walls. In the full example there arefour exterior walls to draw so the data block is H followed by 4triples: Haappphxpfa}}.

The V block, when there are vertical exterior walls to draw, starts witha capital V, followed by three characters for each vertical wall to draw(startX, startY, length). A vertical exterior wall drawn down the leftside is represented as V(0,0,28) as Vaa}. Again, another threecharacters are added for each additional vertical exterior wall to draw.

The h block is similar to the H block except these are rendered ashorizontal interior walls. This block starts with the letter h, followedby three characters for each horizontal line to draw (startX, startY,length). For example, a 15-tile line drawn in the middle is representedas h(0,15,15), which is compactly represented as happ. Another walldrawn in another area appends another block of three coordinates foreach additional wall.

The v block is similar to the V block except these are rendered asvertical interior walls. This block starts with the letter v, followedby three characters for each vertical wall to draw (startX, startY,length).

The t block, when there are interior tiles to draw, starts with theletter t, followed by four characters for each rectangle to draw (x, y,width, height). For example, a 15-tile square is drawn in the corner isrepresented as t(0,0,15,15), which is compactly represented as taapp.Another rectangle of tiles drawn in another area appends another blockof four coordinates. So taapp might become taappap}n.

If there are multiple floors, a semicolon is added and then anotherblock of floor plan data can be added. For an empty floor there can benothing between floors. For example, a three-story house with nothingdefined for the middle floor is represented as follows: 28; HaapppgxpfaVaa}pap}pn; Haapppgxpfa Vaa}pap}pn.

FIG. 62 is an example Home View one-story floor plan, under anembodiment. This floor plan is represented in an embodiment as follows:28 (draw on a grid 28 tiles wide by 28 tiles tall); taappap}n (drawinterior tiles as two large rectangles (x,y,w,h): (0,0,15,15) and(0,15,28,13)); happ (draw an interior horizontal wall (x,y,w):(0,15,15)); vhui (draw an interior vertical wall (x,y,h): (7,20,8));Haappphxpfa}} (draw 4 exterior horizontal walls); Vaa}pap}pn (draw 3vertical exterior walls). The complete homeview/floors data for thissingle-story home would be: 28;taappap}n happ vhui Haappphxpfa}}Vaa}pap}pn.

The homeview/devices variable includes specific data elements, but theembodiments are not so limited. The data elements of an embodimentinclude the following: [device location+id on 1st floor] [another devicelocation+id on 1st floor] [ . . . ] [; device data for 2nd floor] [; 3rdfloor] [; 4th floor] [; 5th floor].

Regarding the device location data element, each device location startswith a letter indicating location type: t (center the device over themiddle of a tile); h (center the device over the middle of a horizontalsegment); v (center the device over the middle of a vertical segment).The device location is followed by two characters that specify the (x,y)location of that tile or wall segment. For example, to place a device inthe center of the first tile an embodiment uses t(0,0), represented astaa.

The device identifier data element is the unique identifier for thedevice. Note that some IDs can be long, so an embodiment only stores thelast six characters of the device ID. For example, if the identifier is“ZONE12VER1”, an embodiment stores “12VER1”, and if the identifier is“ZONE5VER1” the embodiment stores “E5VER1”.

A complete device location+id element is a minimum of four characters(type, x, y, id) and can be up to nine characters. An example of acomplete device location and identification is as follows: Draw camera“SCOFEBED” centered on the third horizontal wall segment across the top:t+(2, 0)+SCOFEBED, stored compactly as tca0FEBED. Another example of acomplete device location and identification is as follows: Draw z-wavelight with ID “7” centered over vertical wall segment 11 across and 5down: vke7.

Data for multiple floors are separated by semicolons as describedherein. Therefore, for a three-story house with just two devices on thethird floor the data is as follows: t{qE5VER1 h{w0FEBED.

FIG. 63 is an example Home View floor plan that includes two devices,under an embodiment. This floor plan is represented in an embodiment asfollows: t{qE5VER1: draw a motion sensor “ZONE5VER1” centered over tileat x,y location (26, 16); h{w0FEBED: draw camera “SCOFEBED” centeredover horizontal wall at x,y location (26, 22). The completehomeview/devices data for this single-story home are: t{qE5VER1h{w0FEBED.

The homeview/labels variable includes specific data elements, but theembodiments are not so limited. The data elements of an embodimentinclude the following: [label location+label text on 1st floor] [anotherlocation+label on 1st floor] [ . . . ] [; label data for 2nd floor] [;3rd floor] [; 4th floor] [; 5th floor].

Each label location data element starts with a letter indicatinglocation type: t (center the label over the middle of a tile; h (centerthe label over the middle of a horizontal segment; v (center the labelover the middle of a vertical segment). The label location data elementis followed by two characters that specify the (x,y) location of thattile or wall segment. For example, to place a label in the center of thefirst tile of an embodiment uses t(0,0), represented as taa.

The label text data element can be almost any string, enclosed inbrackets [ ]. The text encoding of an embodiment follows the W3Cdefinition for encodeURLComponent( ) method in javascript, which encodeseverything except ˜!*( ). The only characters not allowed in labels arebrackets themselves ([ ]). These should be stripped out when labels aredefined in the editor.

Empty labels should not be stored. A complete label location+textelement includes a minimum of six characters (type, x, y, [text]), as invhg[Bedroom].

FIG. 64 is an example Home View floor plan that includes two labels,under an embodiment. This floor plan is represented in an embodiment asfollows: vhg[Bedroom]: draw label “Bedroom” centered over vertical wallat x,y location (7, 6); tsv[Living%20Room]: draw label “Living Room”centered over tile at x,y location (26, 22). The completehomeview/labels data for this single-story home are: vhg[Bedroom]tsv[Living%20Room].

As described in detail herein, the user defines the walls of each floorof a home by drawing basic vectors. However, when a floor is rendered,the building exteriors should be readily distinguished from theinteriors. For rendering Home View, an embodiment includes algorithmsthat determine the interior of the home and compute which tiles shouldbe transparent and which are filled. Perimeter walls are rendered to bemore vivid than interior walls. The user may draw openings in theexternal walls.

The algorithm of an embodiment for determining interior and exteriorwalls begins by marking all tiles as interior tile. A list is generatedof tiles on the edge of each floor that are empty (top row, bottom row,left column, right column), and a function is called to clear each tilehaving no outside wall. Any edge tiles having no walls outside of themare marked as exterior tiles. For each exterior tile, the algorithmrecursively searches the surrounding tiles. If there are no wallsseparating that tile from the next, then the next one is also marked asexterior.

In this way, Home View recursively crawls into the house from the edges,marking tiles as “exterior” as operation proceeds. Once all exteriortiles are determined, walls adjacent to them are also considered“exterior”, and any walls bounded by interior tiles are considered“interior”. The algorithm identifies small openings, before recursingfrom one exterior tile to an adjacent tile, by examining the wallsnearby to ensure the opening is wide enough before proceeding. Thisinterior/exterior computation is computed by the Home View editor, andstored with the floor data on the server. Client renderers have aneasier job since the data indicates interior/exterior information asdefined above in homeview/floors.

The Home View data output from Edit mode is checked to ensure integritythrough performance of the following: the home vectors fit withoutbounds of each floor; all sensors and devices still exist. At the timeof rendering of the home view, the same checks are repeated to verifydata integrity. If any checks fail, a dialog is presented to the user,and the preference returns to the System Icon (the “orb”). The featuretherefore is turned off for display, but the data is still there untilsubsequently edited; if a user attempts to edit home view and the datais corrupted, the user is given the option to reset the data and startover.

The integrated security system includes couplings or connections among avariety of IP devices or components, and the device management module isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system of an embodiment uses a “sandbox” network todiscover and manage all IP devices coupled or connected as components ofthe system. The IP devices of an embodiment include wired devices,wireless devices, cameras, interactive touchscreens, and security panelsto name a few. These devices can be wired via ethernet cable or Wifidevices, all of which are secured within the sandbox network, asdescribed below. The “sandbox” network is described in detail below.

FIG. 65 is a block diagram 500 of network or premise device integrationwith a premise network 250, under an embodiment. In an embodiment,network devices 255-257 are coupled to the gateway 102 using a securenetwork coupling or connection such as SSL over an encrypted 802.11 link(utilizing for example WPA-2 security for the wireless encryption). Thenetwork coupling or connection between the gateway 102 and the networkdevices 255-257 is a private coupling or connection in that it issegregated from any other network couplings or connections. The gateway102 is coupled to the premise router/firewall 252 via a coupling with apremise LAN 250. The premise router/firewall 252 is coupled to abroadband modem 251, and the broadband modem 251 is coupled to a WAN 200or other network outside the premise. The gateway 102 thus enables orforms a separate wireless network, or sub-network, that includes somenumber of devices and is coupled or connected to the LAN 250 of the hostpremises. The gateway sub-network can include, but is not limited to,any number of other devices like WiFi IP cameras, security panels (e.g.,IP-enabled), and security touchscreens, to name a few. The gateway 102manages or controls the sub-network separately from the LAN 250 andtransfers data and information between components of the sub-network andthe LAN 250/WAN 200, but is not so limited. Additionally, other networkdevices 254 can be coupled to the LAN 250 without being coupled to thegateway 102.

FIG. 66 is a block diagram 600 of network or premise device integrationwith a premise network 250, under an alternative embodiment. The networkor premise devices 255-257 are coupled to the gateway 102. The networkcoupling or connection between the gateway 102 and the network devices255-257 is a private coupling or connection in that it is segregatedfrom any other network couplings or connections. The gateway 102 iscoupled or connected between the premise router/firewall 252 and thebroadband modem 251. The broadband modem 251 is coupled to a WAN 200 orother network outside the premise, while the premise router/firewall 252is coupled to a premise LAN 250. As a result of its location between thebroadband modem 251 and the premise router/firewall 252, the gateway 102can be configured or function as the premise router routing specifieddata between the outside network (e.g., WAN 200) and the premiserouter/firewall 252 of the LAN 250. As described above, the gateway 102in this configuration enables or forms a separate wireless network, orsub-network, that includes the network or premise devices 255-257 and iscoupled or connected between the LAN 250 of the host premises and theWAN 200. The gateway sub-network can include, but is not limited to, anynumber of network or premise devices 255-257 like WiFi IP cameras,security panels (e.g., IP-enabled), and security touchscreens, to name afew. The gateway 102 manages or controls the sub-network separately fromthe LAN 250 and transfers data and information between components of thesub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the gateway 102.

The examples described above with reference to FIGS. 47 and 48 arepresented only as examples of IP device integration. The integratedsecurity system is not limited to the type, number and/or combination ofIP devices shown and described in these examples, and any type, numberand/or combination of IP devices is contemplated within the scope ofthis disclosure as capable of being integrated with the premise network.

The integrated security system of an embodiment includes a touchscreen(also referred to as the iControl touchscreen or integrated securitysystem touchscreen), as described above, which provides core securitykeypad functionality, content management and presentation, and embeddedsystems design. The networked security touchscreen system of anembodiment enables a consumer or security provider to easily andautomatically install, configure and manage the security system andtouchscreen located at a customer premise. Using this system thecustomer may access and control the local security system, local IPdevices such as cameras, local sensors and control devices (such aslighting controls or pipe freeze sensors), as well as the local securitysystem panel and associated security sensors (such as door/window,motion, and smoke detectors). The customer premise may be a home,business, and/or other location equipped with a wired or wirelessbroadband IP connection.

The system of an embodiment includes a touchscreen with a configurablesoftware user interface and/or a gateway device (e.g., iHub) thatcouples or connects to a premise security panel through a wired orwireless connection, and a remote server that provides access to contentand information from the premises devices to a user when they are remotefrom the home. The touchscreen supports broadband and/or WAN wirelessconnectivity. In this embodiment, the touchscreen incorporates an IPbroadband connection (e.g., Wifi radio, Ethernet port, etc.), and/or acellular radio (e.g., GPRS/GSM, CDMA, WiMax, etc.). The touchscreendescribed herein can be used as one or more of a security systeminterface panel and a network user interface (UI) that provides aninterface to interact with a network (e.g., LAN, WAN, internet, etc.).

The touchscreen of an embodiment provides an integrated touchscreen andsecurity panel as an all-in-one device. Once integrated using thetouchscreen, the touchscreen and a security panel of a premise securitysystem become physically co-located in one device, and the functionalityof both may even be co-resident on the same CPU and memory (though thisis not required).

The touchscreen of an embodiment also provides an integrated IP videoand touchscreen UI. As such, the touchscreen supports one or morestandard video CODECs/players (e.g., H.264, Flash Video, MOV, MPEG4,M-JPEG, etc.). The touchscreen UI then provides a mechanism (such as acamera or video widget) to play video. In an embodiment the video isstreamed live from an IP video camera. In other embodiments the videocomprises video clips or photos sent from an IP camera or from a remotelocation.

The touchscreen of an embodiment provides a configurable user interfacesystem that includes a configuration supporting use as a securitytouchscreen. In this embodiment, the touchscreen utilizes a modular userinterface that allows components to be modified easily by a serviceprovider, an installer, or even the end user. Examples of such a modularapproach include using Flash widgets, HTML-based widgets, or otherdownloadable code modules such that the user interface of thetouchscreen can be updated and modified while the application isrunning. In an embodiment the touchscreen user interface modules can bedownloaded over the internet. For example, a new security configurationwidget can be downloaded from a standard web server, and the touchscreenthen loads such configuration app into memory, and inserts it in placeof the old security configuration widget. The touchscreen of anembodiment is configured to provide a self-install user interface.

Embodiments of the networked security touchscreen system describedherein include a touchscreen device with a user interface that includesa security toolbar providing one or more functions including arm,disarm, panic, medic, and alert. The touchscreen therefore includes atleast one screen having a separate region of the screen dedicated to asecurity toolbar. The security toolbar of an embodiment is present inthe dedicated region at all times that the screen is active.

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing home-basedfunctions. The home-based functions of an embodiment include managing,viewing, and/or controlling IP video cameras. In this embodiment,regions of the home screen are allocated in the form of widget icons;these widget icons (e.g. for cameras, thermostats, lighting, etc)provide functionality for managing home systems. So, for example, adisplayed camera icon, when selected, launches a Camera Widget, and theCamera widget in turn provides access to video from one or more cameras,as well as providing the user with relevant camera controls (take apicture, focus the camera, etc.)

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing, viewing, and/orcontrolling internet-based content or applications. For example, theWidget Manager UI presents a region of the home screen (up to andincluding the entire home screen) where internet widgets icons such asweather, sports, etc. may be accessed). Each of these icons may beselected to launch their respective content services.

The touchscreen of an embodiment is integrated into a premise networkusing the gateway, as described above. The gateway as described hereinfunctions to enable a separate wireless network, or sub-network, that iscoupled, connected, or integrated with another network (e.g., WAN, LANof the host premises, etc.). The sub-network enabled by the gatewayoptimizes the installation process for IP devices, like the touchscreen,that couple or connect to the sub-network by segregating these IPdevices from other such devices on the network. This segregation of theIP devices of the sub-network further enables separate security andprivacy policies to be implemented for these IP devices so that, wherethe IP devices are dedicated to specific functions (e.g., security), thesecurity and privacy policies can be tailored specifically for thespecific functions. Furthermore, the gateway and the sub-network itforms enables the segregation of data traffic, resulting in faster andmore efficient data flow between components of the host network,components of the sub-network, and between components of the sub-networkand components of the network.

The touchscreen of an embodiment includes a core functional embeddedsystem that includes an embedded operating system, required hardwaredrivers, and an open system interface to name a few. The core functionalembedded system can be provided by or as a component of a conventionalsecurity system (e.g., security system available from GE Security).These core functional units are used with components of the integratedsecurity system as described herein. Note that portions of thetouchscreen description below may include reference to a host premisesecurity system (e.g., GE security system), but these references areincluded only as an example and do not limit the touchscreen tointegration with any particular security system.

As an example, regarding the core functional embedded system, a reducedmemory footprint version of embedded Linux forms the core operatingsystem in an embodiment, and provides basic TCP/IP stack and memorymanagement functions, along with a basic set of low-level graphicsprimitives. A set of device drivers is also provided or included thatoffer low-level hardware and network interfaces. In addition to thestandard drivers, an interface to the RS 485 bus is included thatcouples or connects to the security system panel (e.g., GE Concordpanel). The interface may, for example, implement the Superbus 2000protocol, which can then be utilized by the more comprehensivetransaction-level security functions implemented in PanelConnecttechnology (e.g SetAlarmLevel (int level, int partition, char*accessCode)). Power control drivers are also provided.

FIG. 67 is a block diagram of a touchscreen 700 of the integratedsecurity system, under an embodiment. The touchscreen 700 generallyincludes an application/presentation layer 702 with a residentapplication 704, and a core engine 706. The touchscreen 700 alsoincludes one or more of the following, but is not so limited:applications of premium services 710, widgets 712, a caching proxy 714,network security 716, network interface 718, security object 720,applications supporting devices 722, PanelConnect API 724, a gatewayinterface 726, and one or more ports 728.

More specifically, the touchscreen, when configured as a home securitydevice, includes but is not limited to the following application orsoftware modules: RS 485 and/or RS-232 bus security protocols toconventional home security system panel (e.g., GE Concord panel);functional home security classes and interfaces (e.g. Panel ARM state,Sensor status, etc.); Application/Presentation layer or engine; ResidentApplication; Consumer Home Security Application; installer home securityapplication; core engine; and System bootloader/Software Updater. Thecore Application engine and system bootloader can also be used tosupport other advanced content and applications. This provides aseamless interaction between the premise security application and otheroptional services such as weather widgets or IP cameras.

An alternative configuration of the touchscreen includes a firstApplication engine for premise security and a second Application enginefor all other applications. The integrated security system applicationengine supports content standards such as HTML, XML, Flash, etc. andenables a rich consumer experience for all ‘widgets’, whethersecurity-based or not. The touchscreen thus provides service providersthe ability to use web content creation and management tools to buildand download any ‘widgets’ regardless of their functionality.

As discussed above, although the Security Applications have specificlow-level functional requirements in order to interface with the premisesecurity system, these applications make use of the same fundamentalapplication facilities as any other ‘widget’, application facilitiesthat include graphical layout, interactivity, application handoff,screen management, and network interfaces, to name a few.

Content management in the touchscreen provides the ability to leverageconventional web development tools, performance optimized for anembedded system, service provider control of accessible content, contentreliability in a consumer device, and consistency between ‘widgets’ andseamless widget operational environment. In an embodiment of theintegrated security system, widgets are created by web developers andhosted on the integrated security system Content Manager (and stored inthe Content Store database). In this embodiment the server componentcaches the widgets and offers them to consumers through the web-basedintegrated security system provisioning system. The servers interactwith the advanced touchscreen using HTTPS interfaces controlled by thecore engine and dynamically download widgets and updates as needed to becached on the touchscreen. In other embodiments widgets can be accesseddirectly over a network such as the Internet without needing to gothrough the iControl Content Manager

Referring to FIG. 67 , the touchscreen system is built on a tieredarchitecture, with defined interfaces between theApplication/Presentation Layer (the Application Engine) on the top, theCore Engine in the middle, and the security panel and gateway APIs atthe lower level. The architecture is configured to provide maximumflexibility and ease of maintenance.

The application engine of the touchscreen provides the presentation andinteractivity capabilities for all applications (widgets) that run onthe touchscreen, including both core security function widgets and thirdparty content widgets. FIG. 68 is an example screenshot 800 of anetworked security touchscreen, under an embodiment. This examplescreenshot 800 includes three interfaces or user interface (UI)components 802-806, but is not so limited. A first UI 802 of thetouchscreen includes icons by which a user controls or accessesfunctions and/or components of the security system (e.g., “Main”,“Panic”, “Medic”, “Fire”, state of the premise alarm system (e.g.,disarmed, armed, etc.), etc.); the first UI 802, which is also referredto herein as a security interface, is always presented on thetouchscreen. A second UI 804 of the touchscreen includes icons by whicha user selects or interacts with services and other network content(e.g., clock, calendar, weather, stocks, news, sports, photos, maps,music, etc.) that is accessible via the touchscreen. The second UI 804is also referred to herein as a network interface or content interface.A third UI 806 of the touchscreen includes icons by which a user selectsor interacts with additional services or components (e.g., intercomcontrol, security, cameras coupled to the system in particular regions(e.g., front door, baby, etc.) available via the touchscreen.

A component of the application engine is the Presentation Engine, whichincludes a set of libraries that implement the standards-based widgetcontent (e.g., XML, HTML, JavaScript, Flash) layout and interactivity.This engine provides the widget with interfaces to dynamically load bothgraphics and application logic from third parties, support high leveldata description language as well as standard graphic formats. The setof web content-based functionality available to a widget developer isextended by specific touchscreen functions implemented as local webservices by the Core Engine.

The resident application of the touchscreen is the master service thatcontrols the interaction of all widgets in the system, and enforces thebusiness and security rules required by the service provider. Forexample, the resident application determines the priority of widgets,thereby enabling a home security widget to override resource requestsfrom a less critical widget (e.g. a weather widget). The residentapplication also monitors widget behavior, and responds to client orserver requests for cache updates.

The core engine of the touchscreen manages interaction with othercomponents of the integrated security system, and provides an interfacethrough which the resident application and authorized widgets can getinformation about the home security system, set alarms, install sensors,etc. At the lower level, the Core Engine's main interactions are throughthe PanelConnect API, which handles all communication with the securitypanel, and the gateway Interface, which handles communication with thegateway. In an embodiment, both the iHub Interface and PanelConnect APIare resident and operating on the touchscreen. In another embodiment,the PanelConnect API runs on the gateway or other device that providessecurity system interaction and is accessed by the touchscreen through aweb services interface.

The Core Engine also handles application and service level persistentand cached memory functions, as well as the dynamic provisioning ofcontent and widgets, including but not limited to: flash memorymanagement, local widget and content caching, widget version management(download, cache flush new/old content versions), as well as the cachingand synchronization of user preferences. As a portion of these servicesthe Core engine incorporates the bootloader functionality that isresponsible for maintaining a consistent software image on thetouchscreen, and acts as the client agent for all software updates. Thebootloader is configured to ensure full update redundancy so thatunsuccessful downloads cannot corrupt the integrated security system.

Video management is provided as a set of web services by the CoreEngine. Video management includes the retrieval and playback of localvideo feeds as well as remote control and management of cameras (allthrough iControl CameraConnect technology).

Both the high level application layer and the mid-level core engine ofthe touchscreen can make calls to the network. Any call to the networkmade by the application layer is automatically handed off to a localcaching proxy, which determines whether the request should be handledlocally. Many of the requests from the application layer are webservices API requests; although such requests could be satisfied by theiControl servers, they are handled directly by the touchscreen and thegateway. Requests that get through the caching proxy are checked againsta white list of acceptable sites, and, if they match, are sent offthrough the network interface to the gateway. Included in the NetworkSubsystem is a set of network services including HTTP, HTTPS, andserver-level authentication functions to manage the secure client-serverinterface. Storage and management of certificates is incorporated as apart of the network services layer.

Server components of the integrated security system servers supportinteractive content services on the touchscreen. These server componentsinclude, but are not limited to the content manager, registry manager,network manager, and global registry, each of which is described herein.

The Content Manager oversees aspects of handling widget data and rawcontent on the touchscreen. Once created and validated by the serviceprovider, widgets are ‘ingested’ to the Content Manager, and then becomeavailable as downloadable services through the integrated securitysystem Content Management APIs. The Content manager maintains versionsand timestamp information, and connects to the raw data contained in thebackend Content Store database. When a widget is updated (or new contentbecomes available) all clients registering interest in a widget aresystematically updated as needed (a process that can be configured at anaccount, locale, or system-wide level).

The Registry Manager handles user data, and provisioning accounts,including information about widgets the user has decided to install, andthe user preferences for these widgets.

The Network Manager handles getting and setting state for all devices onthe integrated security system network (e.g., sensors, panels, cameras,etc.). The Network manager synchronizes with the gateway, the advancedtouchscreen, and the subscriber database.

The Global Registry is a primary starting point server for all clientservices, and is a logical referral service that abstracts specificserver locations/addresses from clients (touchscreen, gateway 102,desktop widgets, etc.). This approach enables easy scaling/migration ofserver farms.

The touchscreen of an embodiment operates wirelessly with a premisesecurity system. The touchscreen of an embodiment incorporates an RFtransceiver component that either communicates directly with the sensorsand/or security panel over the panel's proprietary RF frequency, or thetouchscreen communicates wirelessly to the gateway over 802.11,Ethernet, or other IP-based communications channel, as described indetail herein. In the latter case the gateway implements thePanelConnect interface and communicates directly to the security paneland/or sensors over wireless or wired networks as described in detailabove.

The touchscreen of an embodiment is configured to operate with multiplesecurity systems through the use of an abstracted security systeminterface. In this embodiment, the PanelConnect API can be configured tosupport a plurality of proprietary security system interfaces, eithersimultaneously or individually as described herein. In one embodiment ofthis approach, the touchscreen incorporates multiple physical interfacesto security panels (e.g. GE Security RS-485, Honeywell RF, etc.) inaddition to the PanelConnect API implemented to support multiplesecurity interfaces. The change needed to support this in PanelConnectis a configuration parameter specifying the panel type connection thatis being utilized.

So for example, the setARMState( ) function is called with an additionalparameter (e.g., Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”,Parameters=“ExitDelay=30|Lights=OFF”, panelType=“GE Concord4 RS485”)).The ‘panelType’ parameter is used by the setARMState function (and inpractice by all of the PanelConnect functions) to select an algorithmappropriate to the specific panel out of a plurality of algorithms.

The touchscreen of an embodiment is self-installable. Consequently, thetouchscreen provides a ‘wizard’ approach similar to that used intraditional computer installations (e.g. InstallShield). The wizard canbe resident on the touchscreen, accessible through a web interface, orboth. In one embodiment of a touchscreen self-installation process, theservice provider can associate devices (sensors, touchscreens, securitypanels, lighting controls, etc.) remotely using a web-basedadministrator interface.

The touchscreen of an embodiment includes a battery backup system for asecurity touchscreen. The touchscreen incorporates a standard Li-ion orother battery and charging circuitry to allow continued operation in theevent of a power outage. In an embodiment the battery is physicallylocated and connected within the touchscreen enclosure. In anotherembodiment the battery is located as a part of the power transformer, orin between the power transformer and the touchscreen.

The example configurations of the integrated security system describedabove with reference to FIGS. 47 and 48 include a gateway that is aseparate device, and the touchscreen couples to the gateway. However, inan alternative embodiment, the gateway device and its functionality canbe incorporated into the touchscreen so that the device managementmodule, which is now a component of or included in the touchscreen, isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system with the integrated touchscreen/gateway usesthe same “sandbox” network to discover and manage all IP devices coupledor connected as components of the system.

The touchscreen of this alternative embodiment integrates the componentsof the gateway with the components of the touchscreen as describedherein. More specifically, the touchscreen of this alternativeembodiment includes software or applications described above withreference to FIG. 3 . In this alternative embodiment, the touchscreenincludes the gateway application layer 302 as the main program thatorchestrates the operations performed by the gateway. A Security Engine304 of the touchscreen provides robust protection against intentionaland unintentional intrusion into the integrated security system networkfrom the outside world (both from inside the premises as well as fromthe WAN). The Security Engine 304 of an embodiment comprises one or moresub-modules or components that perform functions including, but notlimited to, the following:

-   -   Encryption including 128-bit SSL encryption for gateway and        iConnect server communication to protect user data privacy and        provide secure communication.    -   Bi-directional authentication between the touchscreen and        iConnect server in order to prevent unauthorized spoofing and        attacks. Data sent from the iConnect server to the gateway        application (or vice versa) is digitally signed as an additional        layer of security. Digital signing provides both authentication        and validation that the data has not been altered in transit.    -   Camera SSL encapsulation because picture and video traffic        offered by off-the-shelf networked IP cameras is not secure when        traveling over the Internet. The touchscreen provides for        128-bit SSL encapsulation of the user picture and video data        sent over the internet for complete user security and privacy.    -   802.11b/g/n with WPA-2 security to ensure that wireless camera        communications always takes place using the strongest available        protection.    -   A touchscreen-enabled device is assigned a unique activation key        for activation with an iConnect server. This ensures that only        valid gateway-enabled devices can be activated for use with the        specific instance of iConnect server in use. Attempts to        activate gateway-enabled devices by brute force are detected by        the Security Engine. Partners deploying touchscreen-enabled        devices have the knowledge that only a gateway with the correct        serial number and activation key can be activated for use with        an iConnect server. Stolen devices, devices attempting to        masquerade as gateway-enabled devices, and malicious outsiders        (or insiders as knowledgeable but nefarious customers) cannot        effect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 of the touchscreen allows forseamless and secure updates to the gateway firmware through the iControlMaintenance Application on the server 104, providing a transparent,hassle-free mechanism for the service provider to deploy new featuresand bug fixes to the installed user base. The firmware downloadmechanism is tolerant of connection loss, power interruption and userinterventions (both intentional and unintentional). Such robustnessreduces down time and customer support issues. Touchscreen firmware canbe remotely download either for one touchscreen at a time, a group oftouchscreen, or in batches.

The Automations engine 308 of the touchscreen manages the user-definedrules of interaction between the different devices (e.g. when door opensturn on the light). Though the automation rules are programmed andreside at the portal/server level, they are cached at the gateway levelin order to provide short latency between device triggers and actions.

DeviceConnect 310 of the touchscreen touchscreen includes definitions ofall supported devices (e.g., cameras, security panels, sensors, etc.)using a standardized plug-in architecture. The DeviceConnect module 310offers an interface that can be used to quickly add support for any newdevice as well as enabling interoperability between devices that usedifferent technologies/protocols. For common device types, pre-definedsub-modules have been defined, making supporting new devices of thesetypes even easier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules engine 318 of the touchscreen is responsible for executingthe user defined schedules (e.g., take a picture every five minutes;every day at 8 am set temperature to 65 degrees Fahrenheit, etc.).Though the schedules are programmed and reside at the iConnect serverlevel they are sent to the scheduler within the gateway application ofthe touchscreen. The Schedules Engine 318 then interfaces withSensorConnect 312 to ensure that scheduled events occur at precisely thedesired time. The Device Management module 320 of the touchscreen is incharge of all discovery, installation and configuration of both wiredand wireless IP devices (e.g., cameras, etc.) coupled or connected tothe system. Networked IP devices, such as those used in the integratedsecurity system, require user configuration of many IP and securityparameters, and the device management module of an embodiment handlesthe details of this configuration. The device management module alsomanages the video routing module described below.

The video routing engine 322 of the touchscreen is responsible fordelivering seamless video streams to the user with zero-configuration.Through a multi-step, staged approach the video routing engine uses acombination of UPnP port-forwarding, relay server routing and STUN/TURNpeer-to-peer routing. The video routing engine is described in detail inthe Related Applications.

FIG. 69 is a block diagram 900 of network or premise device integrationwith a premise network 250, under an embodiment. In an embodiment,network devices 255, 256, 957 are coupled to the touchscreen 902 using asecure network connection such as SSL over an encrypted 802.11 link(utilizing for example WPA-2 security for the wireless encryption), andthe touchscreen 902 coupled to the premise router/firewall 252 via acoupling with a premise LAN 250. The premise router/firewall 252 iscoupled to a broadband modem 251, and the broadband modem 251 is coupledto a WAN 200 or other network outside the premise. The touchscreen 902thus enables or forms a separate wireless network, or sub-network, thatincludes some number of devices and is coupled or connected to the LAN250 of the host premises. The touchscreen sub-network can include, butis not limited to, any number of other devices like WiFi IP cameras,security panels (e.g., IP-enabled), and IP devices, to name a few. Thetouchscreen 902 manages or controls the sub-network separately from theLAN 250 and transfers data and information between components of thesub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the touchscreen 902.

FIG. 70 is a block diagram 1000 of network or premise device integrationwith a premise network 250, under an alternative embodiment. The networkor premise devices 255, 256, 1057 are coupled to the touchscreen 1002,and the touchscreen 1002 is coupled or connected between the premiserouter/firewall 252 and the broadband modem 251. The broadband modem 251is coupled to a WAN 200 or other network outside the premise, while thepremise router/firewall 252 is coupled to a premise LAN 250. As a resultof its location between the broadband modem 251 and the premiserouter/firewall 252, the touchscreen 1002 can be configured or functionas the premise router routing specified data between the outside network(e.g., WAN 200) and the premise router/firewall 252 of the LAN 250. Asdescribed above, the touchscreen 1002 in this configuration enables orforms a separate wireless network, or sub-network, that includes thenetwork or premise devices 255, 156, 1057 and is coupled or connectedbetween the LAN 250 of the host premises and the WAN 200. Thetouchscreen sub-network can include, but is not limited to, any numberof network or premise devices 255, 256, 1057 like WiFi IP cameras,security panels (e.g., IP-enabled), and security touchscreens, to name afew. The touchscreen 1002 manages or controls the sub-network separatelyfrom the LAN 250 and transfers data and information between componentsof the sub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the touchscreen 1002.

The gateway of an embodiment, whether a stand-along component orintegrated with a touchscreen, enables couplings or connections and thusthe flow or integration of information between various components of thehost premises and various types and/or combinations of IP devices, wherethe components of the host premises include a network (e.g., LAN) and/ora security system or subsystem to name a few. Consequently, the gatewaycontrols the association between and the flow of information or databetween the components of the host premises. For example, the gateway ofan embodiment forms a sub-network coupled to another network (e.g., WAN,LAN, etc.), with the sub-network including IP devices. The gatewayfurther enables the association of the IP devices of the sub-networkwith appropriate systems on the premises (e.g., security system, etc.).Therefore, for example, the gateway can form a sub-network of IP devicesconfigured for security functions, and associate the sub-network onlywith the premises security system, thereby segregating the IP devicesdedicated to security from other IP devices that may be coupled toanother network on the premises.

The gateway of an embodiment, as described herein, enables couplings orconnections and thus the flow of information between various componentsof the host premises and various types and/or combinations of IPdevices, where the components of the host premises include a network, asecurity system or subsystem to name a few. Consequently, the gatewaycontrols the association between and the flow of information or databetween the components of the host premises. For example, the gateway ofan embodiment forms a sub-network coupled to another network (e.g., WAN,LAN, etc.), with the sub-network including IP devices. The gatewayfurther enables the association of the IP devices of the sub-networkwith appropriate systems on the premises (e.g., security system, etc.).Therefore, for example, the gateway can form a sub-network of IP devicesconfigured for security functions, and associate the sub-network onlywith the premises security system, thereby segregating the IP devicesdedicated to security from other IP devices that may be coupled toanother network on the premises.

FIG. 71 is a flow diagram for a method 1100 of forming a securitynetwork including integrated security system components, under anembodiment. Generally, the method comprises coupling 1102 a gatewaycomprising a connection management component to a local area network ina first location and a security server in a second location. The methodcomprises forming 1104 a security network by automatically establishinga wireless coupling between the gateway and a security system using theconnection management component. The security system of an embodimentcomprises security system components located at the first location. Themethod comprises integrating 1106 communications and functions of thesecurity system components into the security network via the wirelesscoupling.

FIG. 72 is a flow diagram for a method 1200 of forming a securitynetwork including integrated security system components and networkdevices, under an embodiment. Generally, the method comprises coupling1202 a gateway to a local area network located in a first location and asecurity server in a second location. The method comprises automaticallyestablishing 1204 communications between the gateway and security systemcomponents at the first location, the security system including thesecurity system components. The method comprises automaticallyestablishing 1206 communications between the gateway and premise devicesat the first location. The method comprises forming 1208 a securitynetwork by electronically integrating, via the gateway, communicationsand functions of the premise devices and the security system components.

In an example embodiment, FIG. 73 is a flow diagram 1300 for integrationor installation of an IP device into a private network environment,under an embodiment. The IP device includes any IP-capable device that,for example, includes the touchscreen of an embodiment. The variables ofan embodiment set at time of installation include, but are not limitedto, one or more of a private SSID/Password, a gateway identifier, asecurity panel identifier, a user account TS, and a Central MonitoringStation account identification.

An embodiment of the IP device discovery and management begins with auser or installer activating 1302 the gateway and initiating 1304 theinstall mode of the system. This places the gateway in an install mode.Once in install mode, the gateway shifts to a default (Install) Wificonfiguration. This setting will match the default setting for otherintegrated security system-enabled devices that have been pre-configuredto work with the integrated security system. The gateway will then beginto provide 1306 DHCP addresses for these IP devices. Once the deviceshave acquired a new DHCP address from the gateway, those devices areavailable for configuration into a new secured Wifi network setting.

The user or installer of the system selects 1308 all devices that havebeen identified as available for inclusion into the integrated securitysystem. The user may select these devices by their unique IDs via a webpage, Touchscreen, or other client interface. The gateway provides 1310data as appropriate to the devices. Once selected, the devices areconfigured 1312 with appropriate secured Wifi settings, including SSIDand WPA/WPA-2 keys that are used once the gateway switches back to thesecured sandbox configuration from the “Install” settings. Othersettings are also configured as appropriate for that type of device.Once all devices have been configured, the user is notified and the usercan exit install mode. At this point all devices will have beenregistered 1314 with the integrated security system servers.

The installer switches 1316 the gateway to an operational mode, and thegateway instructs or directs 1318 all newly configured devices to switchto the “secured” Wifi sandbox settings. The gateway then switches 1320to the “secured” Wifi settings. Once the devices identify that thegateway is active on the “secured” network, they request new DHCPaddresses from the gateway which, in response, provides 1322 the newaddresses. The devices with the new addresses are then operational 1324on the secured network.

In order to ensure the highest level of security on the secured network,the gateway can create or generate a dynamic network securityconfiguration based on the unique ID and private key in the gateway,coupled with a randomizing factor that can be based on online time orother inputs. This guarantees the uniqueness of the gateway securednetwork configuration.

To enable the highest level of performance, the gateway analyzes the RFspectrum of the 802.11x network and determines which frequencyband/channel it should select to run.

An alternative embodiment of the camera/IP device management processleverages the local ethernet connection of the sandbox network on thegateway. This alternative process is similar to the Wifi discoveryembodiment described above, except the user connects the targeted deviceto the ethernet port of the sandbox network to begin the process. Thisalternative embodiment accommodates devices that have not beenpre-configured with the default “Install” configuration for theintegrated security system.

This alternative embodiment of the IP device discovery and managementbegins with the user/installer placing the system into install mode. Theuser is instructed to attach an IP device to be installed to the sandboxEthernet port of the gateway. The IP device requests a DHCP address fromthe gateway which, in response to the request, provides the address. Theuser is presented the device and is asked if he/she wants to install thedevice. If yes, the system configures the device with the secured Wifisettings and other device-specific settings (e.g., camera settings forvideo length, image quality etc.). The user is next instructed todisconnect the device from the ethernet port. The device is nowavailable for use on the secured sandbox network.

FIG. 74 is a block diagram showing communications among integrated IPdevices of the private network environment, under an embodiment. The IPdevices of this example include a security touchscreen 1403, gateway1402 (e.g., “iHub”), and security panel (e.g., “Security Panel 1”,“Security Panel 2”, “Security Panel n”), but the embodiment is not solimited. In alternative embodiments any number and/or combination ofthese three primary component types may be combined with othercomponents including IP devices and/or security system components. Forexample, a single device which comprises an integrated gateway,touchscreen, and security panel is merely another embodiment of theintegrated security system described herein. The description thatfollows includes an example configuration that includes a touchscreenhosting particular applications. However, the embodiment is not limitedto the touchscreen hosting these applications, and the touchscreenshould be thought of as representing any IP device.

Referring to FIG. 74 , the touchscreen 1403 incorporates an application1410 that is implemented as computer code resident on the touchscreenoperating system, or as a web-based application running in a browser, oras another type of scripted application (e.g., Flash, Java, VisualBasic, etc.). The touchscreen core application 1410 represents thisapplication, providing user interface and logic for the end user tomanage their security system or to gain access to networked informationor content (Widgets). The touchscreen core application 1410 in turnaccesses a library or libraries of functions to control the localhardware (e.g. screen display, sound, LEDs, memory, etc.) as well asspecialized librarie(s) to couple or connect to the security system.

In an embodiment of this security system connection, the touchscreen1403 communicates to the gateway 1402, and has no direct communicationwith the security panel. In this embodiment, the touchscreen coreapplication 1410 accesses the remote service APIs 1412 which providesecurity system functionality (e.g. ARM/DISARM panel, sensor state,get/set panel configuration parameters, initiate or get alarm events,etc.). In an embodiment, the remote service APIs 1412 implement one ormore of the following functions, but the embodiment is not so limited:Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”,Parameters=“ExitDelay=30|Lights=OFF”);sensorState=getSensors(type=“ALL|SensorName|SensorNameList”);result=setSensorState(SensorName, parameters=“Option1, Options2, . . .Option n”); interruptHandler=SensorEvent( ); and,interruptHandler=alarmEvent( ).

Functions of the remote service APIs 1412 of an embodiment use a remotePanelConnect API 1424 which resides in memory on the gateway 1402. Thetouchscreen 1403 communicates with the gateway 1402 through a suitablenetwork interface such as an Ethernet or 802.11 RF connection, forexample. The remote PanelConnect API 1424 provides the underlyingSecurity System Interfaces 1426 used to communicate with and control oneor more types of security panel via wired link 1430 and/or RF link 3.The PanelConnect API 1224 provides responses and input to the remoteservices APIs 1426, and in turn translates function calls and data toand from the specific protocols and functions supported by a specificimplementation of a Security Panel (e.g. a GE Security Simon XT orHoneywell Vista 20P). In an embodiment, the PanelConnect API 1224 uses a345 MHz RF transceiver or receiver hardware/firmware module tocommunicate wirelessly to the security panel and directly to a set of345 MHz RF-enabled sensors and devices, but the embodiment is not solimited.

The gateway of an alternative embodiment communicates over a wiredphysical coupling or connection to the security panel using the panel'sspecific wired hardware (bus) interface and the panel's bus-levelprotocol.

In an alternative embodiment, the Touchscreen 1403 implements the samePanelConnect API 1414 locally on the Touchscreen 1403, communicatingdirectly with the Security Panel 2 and/or Sensors 2 over the proprietaryRF link or over a wired link for that system. In this embodiment theTouchscreen 1403, instead of the gateway 1402, incorporates the 345 MHzRF transceiver to communicate directly with Security Panel 2 or Sensors2 over the RF link 2. In the case of a wired link the Touchscreen 1403incorporates the real-time hardware (e.g. a PIC chip and RS232-variantserial link) to physically connect to and satisfy the specific bus-leveltiming requirements of the SecurityPanel2.

In yet another alternative embodiment, either the gateway 1402 or theTouchscreen 1403 implements the remote service APIs. This embodimentincludes a Cricket device (“Cricket”) which comprises but is not limitedto the following components: a processor (suitable for handling 802.11protocols and processing, as well as the bus timing requirements ofSecurityPanel1); an 802.11 (WiFi) client IP interface chip; and, aserial bus interface chip that implements variants of RS232 or RS485,depending on the specific Security Panel.

The Cricket also implements the full PanelConnect APIs such that it canperform the same functions as the case where the gateway implements thePanelConnect APIs. In this embodiment, the touchscreen core application1410 calls functions in the remote service APIs 1412 (such assetArmState( )). These functions in turn couple or connect to the remoteCricket through a standard IP connection (“Cricket IP Link”) (e.g.,Ethernet, Homeplug, the gateway's proprietary Wifi network, etc.). TheCricket in turn implements the PanelConnect API, which responds to therequest from the touchscreen core application, and performs theappropriate function using the proprietary panel interface. Thisinterface uses either the wireless or wired proprietary protocol for thespecific security panel and/or sensors.

FIG. 75 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment. Operations begin when the system is powered on1510, involving at a minimum the power-on of the gateway device, andoptionally the power-on of the connection between the gateway device andthe remote servers. The gateway device initiates 1520 a software and RFsequence to locate the extant security system. The gateway and installerinitiate and complete 1530 a sequence to ‘learn’ the gateway into thesecurity system as a valid and authorized control device. The gatewayinitiates 1540 another software and RF sequence of instructions todiscover and learn the existence and capabilities of existing RF deviceswithin the extant security system, and store this information in thesystem. These operations under the system of an embodiment are describedin further detail below.

Unlike conventional systems that extend an existing security system, thesystem of an embodiment operates utilizing the proprietary wirelessprotocols of the security system manufacturer. In one illustrativeembodiment, the gateway is an embedded computer with an IP LAN and WANconnection and a plurality of RF transceivers and software protocolmodules capable of communicating with a plurality of security systemseach with a potentially different RF and software protocol interface.After the gateway has completed the discovery and learning 1540 ofsensors and has been integrated 1550 as a virtual control device in theextant security system, the system becomes operational. Thus, thesecurity system and associated sensors are presented 1550 as accessibledevices to a potential plurality of user interface subsystems.

The system of an embodiment integrates 1560 the functionality of theextant security system with other non-security devices including but notlimited to IP cameras, touchscreens, lighting controls, door lockingmechanisms, which may be controlled via RF, wired, or powerline-basednetworking mechanisms supported by the gateway or servers.

The system of an embodiment provides a user interface subsystem 1570enabling a user to monitor, manage, and control the system andassociated sensors and security systems. In an embodiment of the system,a user interface subsystem is an HTML/XML/Javascript/Java/AJAX/Flashpresentation of a monitoring and control application, enabling users toview the state of all sensors and controllers in the extant securitysystem from a web browser or equivalent operating on a computer, PDA,mobile phone, or other consumer device.

In another illustrative embodiment of the system described herein, auser interface subsystem is an HTML/XML/Javascript/Java/AJAXpresentation of a monitoring and control application, enabling users tocombine the monitoring and control of the extant security system andsensors with the monitoring and control of non-security devicesincluding but not limited to IP cameras, touchscreens, lightingcontrols, door locking mechanisms.

In another illustrative embodiment of the system described herein, auser interface subsystem is a mobile phone application enabling users tomonitor and control the extant security system as well as othernon-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application running on a keypad ortouchscreen device enabling users to monitor and control the extantsecurity system as well as other non-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application operating on a TV or set-topbox connected to a TV enabling users to monitor and control the extantsecurity system as well as other non-security devices.

FIG. 76 is a block diagram of an integrated security system 1600wirelessly interfacing to proprietary security systems, under anembodiment. A security system 1610 is coupled or connected to a Gateway1620, and from Gateway 1620 coupled or connected to a plurality ofinformation and content sources across a network 1630 including one ormore web servers 1640, system databases 1650, and applications servers1660. While in one embodiment network 1630 is the Internet, includingthe World Wide Web, those of skill in the art will appreciate thatnetwork 1630 may be any type of network, such as an intranet, anextranet, a virtual private network (VPN), a mobile network, or anon-TCP/IP based network.

Moreover, other elements of the system of an embodiment may beconventional, well-known elements that need not be explained in detailherein. For example, security system 1610 could be any type home orbusiness security system, such devices including but not limited to astandalone RF home security system or a non-RF-capable wired homesecurity system with an add-on RF interface module. In the integratedsecurity system 1600 of this example, security system 1610 includes anRF-capable wireless security panel (WSP) 1611 that acts as the mastercontroller for security system 1610. Well-known examples of such a WSPinclude the GE Security Concord, Networx, and Simon panels, theHoneywell Vista and Lynx panels, and similar panels from DSC and Napco,to name a few. A wireless module 1614 includes the RF hardware andprotocol software necessary to enable communication with and control ofa plurality of wireless devices 1613. WSP 1611 may also manage wireddevices 1614 physically connected to WSP 1611 with an RS232 or RS485 orEthernet connection or similar such wired interface.

In an implementation consistent with the systems and methods describedherein, Gateway 1620 provides the interface between security system 1610and LAN and/or WAN for purposes of remote control, monitoring, andmanagement. Gateway 1620 communicates with an external web server 1640,database 1650, and application server 1660 over network 1630 (which maycomprise WAN, LAN, or a combination thereof). In this example system,application logic, remote user interface functionality, as well as userstate and account are managed by the combination of these remoteservers. Gateway 1620 includes server connection manager 1621, asoftware interface module responsible for all server communication overnetwork 1630. Event manager 1622 implements the main event loop forGateway 1620, processing events received from device manager 1624(communicating with non-security system devices including but notlimited to IP cameras, wireless thermostats, or remote door locks).Event manager 1622 further processes events and control messages fromand to security system 1610 by utilizing WSP manager 1623.

WSP manager 1623 and device manager 1624 both rely upon wirelessprotocol manager 1626 which receives and stores the proprietary orstandards-based protocols required to support security system 1610 aswell as any other devices interfacing with gateway 1620. WSP manager1623 further utilizes the comprehensive protocols and interfacealgorithms for a plurality of security systems 1610 stored in the WSP DBclient database associated with wireless protocol manager 1626. Thesevarious components implement the software logic and protocols necessaryto communicate with and manager devices and security systems 1610.Wireless Transceiver hardware modules 1625 are then used to implementthe physical RF communications link to such devices and security systems1610. An illustrative wireless transceiver 1625 is the GE SecurityDialog circuit board, implementing a 319.5 MHz two-way RF transceivermodule. In this example, RF Link 1670 represents the 319.5 MHz RFcommunication link, enabling gateway 1620 to monitor and control WSP1611 and associated wireless and wired devices 1613 and 1614,respectively.

In one embodiment, server connection manager 1621 requests and receivesa set of wireless protocols for a specific security system 1610 (anillustrative example being that of the GE Security Concord panel andsensors) and stores them in the WSP DB portion of the wireless protocolmanager 1626. WSP manager 1623 then utilizes such protocols fromwireless protocol manager 1626 to initiate the sequence of processesdetailed in FIG. 57 and FIG. 58 for learning gateway 1620 into securitysystem 1610 as an authorized control device. Once learned in, asdescribed with reference to FIG. 58 (and above), event manager 1622processes all events and messages detected by the combination of WSPmanager 1623 and the GE Security wireless transceiver module 1625.

In another embodiment, gateway 1620 incorporates a plurality of wirelesstransceivers 1625 and associated protocols managed by wireless protocolmanager 1626. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1611, wireless devices1613, and wired devices 1614. For example a wireless sensor from onemanufacturer may be utilized to control a device using a differentprotocol from a different manufacturer.

In another embodiment, gateway 1620 incorporates a wired interface tosecurity system 1610, and incorporates a plurality of wirelesstransceivers 1625 and associated protocols managed by wireless protocolmanager 1626. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1611, wireless devices1613, and wired devices 1614.

Of course, while an illustrative embodiment of an architecture of thesystem of an embodiment is described in detail herein with respect toFIG. 58 , one of skill in the art will understand that modifications tothis architecture may be made without departing from the scope of thedescription presented herein. For example, the functionality describedherein may be allocated differently between client and server, oramongst different server or processor-based components. Likewise, theentire functionality of the gateway 1620 described herein could beintegrated completely within an existing security system 1610. In suchan embodiment, the architecture could be directly integrated with asecurity system 1610 in a manner consistent with the currently describedembodiments.

FIG. 77 is a flow diagram for wirelessly ‘learning’ the Gateway into anexisting security system and discovering extant sensors, under anembodiment. The learning interfaces gateway 1620 with security system1610. Gateway 1620 powers up 1710 and initiates software sequences 1720and 1725 to identify accessible WSPs 1611 and wireless devices 1613,respectively (e.g., one or more WSPs and/or devices within range ofgateway 1620). Once identified, WSP 1611 is manually or automaticallyset into ‘learn mode’ 1730, and gateway 1620 utilizes availableprotocols to add 1740 itself as an authorized control device in securitysystem 1610. Upon successful completion of this task, WSP 1611 ismanually or automatically removed from ‘learn mode’ 1750.

Gateway 1620 utilizes the appropriate protocols to mimic 1760 the firstidentified device 1614. In this operation gateway 1620 identifies itselfusing the unique or pseudo-unique identifier of the first found device1614, and sends an appropriate change of state message over RF Link1670. In the event that WSP 1611 responds to this change of statemessage, the device 1614 is then added 1770 to the system in database1650. Gateway 1620 associates 1780 any other information (such as zonename or token-based identifier) with this device 1614 in database 1650,enabling gateway 1620, user interface modules, or any application toretrieve this associated information.

In the event that WSP 1611 does not respond to the change of statemessage, the device 1614 is not added 1770 to the system in database1650, and this device 1614 is identified as not being a part of securitysystem 1610 with a flag, and is either ignored or added as anindependent device, at the discretion of the system provisioning rules.Operations hereunder repeat 1785 operations 1760, 1770, 1780 for alldevices 1614 if applicable. Once all devices 1614 have been tested inthis way, the system begins operation 1790.

In another embodiment, gateway 1620 utilizes a wired connection to WSP1611, but also incorporates a wireless transceiver 1625 to communicatedirectly with devices 1614. In this embodiment, operations under 1720above are removed, and operations under 1740 above are modified so thesystem of this embodiment utilizes wireline protocols to add itself asan authorized control device in security system 1610.

A description of an example embodiment follows in which the Gateway(FIG. 58 , element 1620) is the iHub available from iControl Networks,Palo Alto, Calif., and described in detail herein. In this example thegateway is “automatically” installed with a security system.

The automatic security system installation begins with the assignment ofan authorization key to components of the security system (e.g.,gateway, kit including the gateway, etc.). The assignment of anauthorization key is done in lieu of creating a user account. Aninstaller later places the gateway in a user's premises along with thepremises security system. The installer uses a computer to navigate to aweb portal (e.g., integrated security system web interface), logs in tothe portal, and enters the authorization key of the installed gatewayinto the web portal for authentication. Once authenticated, the gatewayautomatically discovers devices at the premises (e.g., sensors, cameras,light controls, etc.) and adds the discovered devices to the system or“network”. The installer assigns names to the devices, and testsoperation of the devices back to the server (e.g., did the door open,did the camera take a picture, etc.). The security device information isoptionally pushed or otherwise propagated to a security panel and/or tothe server network database. The installer finishes the installation,and instructs the end user on how to create an account, username, andpassword. At this time the user enters the authorization key whichvalidates the account creation (uses a valid authorization key toassociate the network with the user's account). New devices maysubsequently be added to the security network in a variety of ways(e.g., user first enters a unique ID for each device/sensor and names itin the server, after which the gateway can automatically discover andconfigure the device).

A description of another example embodiment follows in which thesecurity system (FIG. 58 , element 1610) is a Dialog system and the WSP(FIG. 58 , element 1611) is a SimonXT available from General ElectricSecurity, and the Gateway (FIG. 58, element 1620) is the iHub availablefrom iControl Networks, Palo Alto, Calif., and described in detailherein. Descriptions of the install process for the SimonXT and iHub arealso provided below.

GE Security's Dialog network is one of the most widely deployed andtested wireless security systems in the world. The physical RF networkis based on a 319.5 MHz unlicensed spectrum, with a bandwidth supportingup to 19 Kbps communications. Typical use of this bandwidth—even inconjunction with the integrated security system—is far less than that.Devices on this network can support either one-way communication (eithera transmitter or a receiver) or two-way communication (a transceiver).Certain GE Simon, Simon XT, and Concord security control panelsincorporate a two-way transceiver as a standard component. The gatewayalso incorporates the same two-way transceiver card. The physical linklayer of the network is managed by the transceiver module hardware andfirmware, while the coded payload bitstreams are made available to theapplication layer for processing.

Sensors in the Dialog network typically use a 60-bit protocol forcommunicating with the security panel transceiver, while security systemkeypads and the gateway use the encrypted 80-bit protocol. The Dialognetwork is configured for reliability, as well as low-power usage. Manydevices are supervised, i.e. they are regularly monitored by the system‘master’ (typically a GE security panel), while still maintainingexcellent power usage characteristics. A typical door window sensor hasa battery life in excess of 5-7 years.

The gateway has two modes of operation in the Dialog network: a firstmode of operation is when the gateway is configured or operates as a‘slave’ to the GE security panel; a second mode of operation is when thegateway is configured or operates as a ‘master’ to the system in theevent a security panel is not present. In both configurations, thegateway has the ability to ‘listen’ to network traffic, enabling thegateway to continually keep track of the status of all devices in thesystem. Similarly, in both situations the gateway can address andcontrol devices that support setting adjustments (such as the GEwireless thermostat).

In the configuration in which the gateway acts as a ‘slave’ to thesecurity panel, the gateway is ‘learned into’ the system as a GEwireless keypad. In this mode of operation, the gateway emulates asecurity system keypad when managing the security panel, and can querythe security panel for status and ‘listen’ to security panel events(such as alarm events).

The gateway incorporates an RF Transceiver manufactured by GE Security,but is not so limited. This transceiver implements the Dialog protocolsand handles all network message transmissions, receptions, and timing.As such, the physical, link, and protocol layers of the communicationsbetween the gateway and any GE device in the Dialog network are totallycompliant with GE Security specifications.

At the application level, the gateway emulates the behavior of a GEwireless keypad utilizing the GE Security 80-bit encrypted protocol, andonly supported protocols and network traffic are generated by thegateway. Extensions to the Dialog RF protocol of an embodiment enablefull control and configuration of the panel, and iControl can bothautomate installation and sensor enrollment as well as directconfiguration downloads for the panel under these protocol extensions.

As described above, the gateway participates in the GE Security networkat the customer premises. Because the gateway has intelligence and atwo-way transceiver, it can ‘hear’ all of the traffic on that network.The gateway makes use of the periodic sensor updates, state changes, andsupervisory signals of the network to maintain a current state of thepremises. This data is relayed to the integrated security system server(e.g., FIG. 2 , element 260) and stored in the event repository for useby other server components. This usage of the GE Security RF network iscompletely non-invasive; there is no new data traffic created to supportthis activity.

The gateway can directly (or indirectly through the Simon XT panel)control two-way devices on the network. For example, the gateway candirect a GE Security Thermostat to change its setting to ‘Cool’ from‘Off’, as well as request an update on the current temperature of theroom. The gateway performs these functions using the existing GE Dialogprotocols, with little to no impact on the network; a gateway devicecontrol or data request takes only a few dozen bytes of data in anetwork that can support 19 Kbps.

By enrolling with the Simon XT as a wireless keypad, as describedherein, the gateway includes data or information of all alarm events, aswell as state changes relevant to the security panel. This informationis transferred to the gateway as encrypted packets in the same way thatthe information is transferred to all other wireless keypads on thenetwork.

Because of its status as an authorized keypad, the gateway can alsoinitiate the same panel commands that a keypad can initiate. Forexample, the gateway can arm or disarm the panel using the standardDialog protocol for this activity. Other than the monitoring of standardalarm events like other network keypads, the only incremental datatraffic on the network as a result of the gateway is the infrequentremote arm/disarm events that the gateway initiates, or infrequentqueries on the state of the panel.

The gateway is enrolled into the Simon XT panel as a ‘slave’ devicewhich, in an embodiment, is a wireless keypad. This enables the gatewayfor all necessary functionality for operating the Simon XT systemremotely, as well as combining the actions and information ofnon-security devices such as lighting or door locks with GE Securitydevices. The only resource taken up by the gateway in this scenario isone wireless zone (sensor ID).

The gateway of an embodiment supports three forms of sensor and panelenrollment/installation into the integrated security system, but is notlimited to this number of enrollment/installation options. Theenrollment/installation options of an embodiment include installerinstallation, kitting, and panel, each of which is described below.

Under the installer option, the installer enters the sensor IDs at timeof installation into the integrated security system web portal oriScreen. This technique is supported in all configurations andinstallations.

Kits can be pre-provisioned using integrated security systemprovisioning applications when using the kitting option. At kittingtime, multiple sensors are automatically associated with an account, andat install time there is no additional work required.

In the case where a panel is installed with sensors already enrolled(i.e. using the GE Simon XT enrollment process), the gateway has thecapability to automatically extract the sensor information from thesystem and incorporate it into the user account on the integratedsecurity system server.

The gateway and integrated security system of an embodiment uses anauto-learn process for sensor and panel enrollment in an embodiment. Thedeployment approach of an embodiment can use additional interfaces thatGE Security is adding to the Simon XT panel. With these interfaces, thegateway has the capability to remotely enroll sensors in the panelautomatically. The interfaces include, but are not limited to, thefollowing: EnrollDevice(ID, type, name, zone, group);SetDeviceParameters(ID, type, Name, zone, group),GetDeviceParameters(zone); and RemoveDevice(zone).

The integrated security system incorporates these new interfaces intothe system, providing the following install process. The install processcan include integrated security system logistics to handle kitting andpre-provisioning. Pre-kitting and logistics can include apre-provisioning kitting tool provided by integrated security systemthat enables a security system vendor or provider (“provider”) to offerpre-packaged initial ‘kits’. This is not required but is recommended forsimplifying the install process. This example assumes a ‘Basic’ kit ispreassembled and includes one (1) Simon XT, three (3) Door/windowsensors, one (1) motion sensor, one (1) gateway, one (1) keyfob, two (2)cameras, and ethernet cables. The kit also includes a sticker page withall Zones (1-24) and Names (full name list).

The provider uses the integrated security system kitting tool toassemble ‘Basic’ kit packages. The contents of different types ofstarter kits may be defined by the provider. At the distributionwarehouse, a worker uses a bar code scanner to scan each sensor and thegateway as it is packed into the box. An ID label is created that isattached to the box. The scanning process automatically associates allthe devices with one kit, and the new ID label is the unique identifierof the kit. These boxes are then sent to the provider for distributionto installer warehouses. Individual sensors, cameras, etc. are also sentto the provider installer warehouse. Each is labeled with its ownbarcode/ID.

An installation and enrollment procedure of a security system includinga gateway is described below as one example of the installation process.

-   1. Order and Physical Install Process    -   a. Once an order is generated in the iControl system, an account        is created and an install ticket is created and sent        electronically to the provider for assignment to an installer.    -   b. The assigned installer picks up his/her ticket(s) and fills        his/her truck with Basic and/or Advanced starter kits. He/she        also keeps a stock of individual sensors, cameras, iHubs, Simon        XTs, etc. Optionally, the installer can also stock homeplug        adapters for problematic installations.    -   c. The installer arrives at the address on the ticket, and pulls        out the Basic kit. The installer determines sensor locations        from a tour of the premises and discussion with the homeowner.        At this point assume the homeowner requests additional equipment        including an extra camera, two (2) additional door/window        sensors, one (1) glass break detector, and one (1) smoke        detector.    -   d. Installer mounts SimonXT in the kitchen or other location in        the home as directed by the homeowner, and routes the phone line        to Simon XT if available. GPRS and Phone numbers pre-programmed        in SimonXT to point to the provider Central Monitoring Station        (CMS).    -   e. Installer places gateway in the home in the vicinity of a        router and cable modem. Installer installs an ethernet line from        gateway to router and plugs gateway into an electrical outlet.-   2. Associate and Enroll gateway into SimonXT    -   a. Installer uses either his/her own laptop plugged into router,        or homeowners computer to go to the integrated security system        web interface and log in with installer ID/pass.    -   b. Installer enters ticket number into admin interface, and        clicks ‘New Install’ button. Screen prompts installer for kit ID        (on box's barcode label).    -   c. Installer clicks ‘Add SimonXT’. Instructions prompt installer        to put Simon XT into install mode, and add gateway as a wireless        keypad. It is noted that this step is for security only and can        be automated in an embodiment.    -   d. Installer enters the installer code into the Simon XT.        Installer Learns ‘gateway’ into the panel as a wireless keypad        as a group 1 device.    -   e. Installer goes back to Web portal, and clicks the ‘Finished        Adding SimonXT’ button.-   3. Enroll Sensors into SimonXT via iControl    -   a. All devices in the Basic kit are already associated with the        user's account.    -   b. For additional devices, Installer clicks ‘Add Device’ and        adds the additional camera to the user's account (by typing in        the camera ID/Serial #).    -   c. Installer clicks ‘Add Device’ and adds other sensors (two (2)        door/window sensors, one (1) glass break sensor, and one (1)        smoke sensor) to the account (e.g., by typing in IDs).    -   d. As part of Add Device, Installer assigns zone, name, and        group to the sensor. Installer puts appropriate Zone and Name        sticker on the sensor temporarily.    -   e. All sensor information for the account is pushed or otherwise        propagated to the iConnect server, and is available to propagate        to CMS automation software through the CMS application        programming interface (API).    -   f. Web interface displays ‘Installing Sensors in System . . . ’        and automatically adds all of the sensors to the Simon XT panel        through the GE RF link.    -   g. Web interface displays ‘Done Installing’->all sensors show        green.-   4. Place and Tests Sensors in Home    -   a. Installer physically mounts each sensor in its desired        location, and removes the stickers.    -   b. Installer physically mounts WiFi cameras in their location        and plugs into AC power. Optional fishing of low voltage wire        through wall to remove dangling wires. Camera transformer is        still plugged into outlet but wire is now inside the wall.    -   c. Installer goes to Web interface and is prompted for automatic        camera install. Each camera is provisioned as a private,        encrypted Wifi device on the gateway secured sandbox network,        and firewall NAT traversal is initiated. Upon completion the        customer is prompted to test the security system.    -   d. Installer selects the ‘Test System’ button on the web        portal—the SimonXT is put into Test mode by the gateway over GE        RF.    -   e. Installer manually tests the operation of each sensor,        receiving an audible confirmation from SimonXT.    -   f. gateway sends test data directly to CMS over broadband link,        as well as storing the test data in the user's account for        subsequent report generation.    -   g. Installer exits test mode from the Web portal.-   5. Installer instructs customer on use of the Simon XT, and shows    customer how to log into the iControl web and mobile portals.    Customer creates a username/password at this time.-   6. Installer instructs customer how to change Simon XT user code    from the Web interface. Customer changes user code which is pushed    to SimonXT automatically over GE RF.

An installation and enrollment procedure of a security system includinga gateway is described below as an alternative example of theinstallation process. This installation process is for use for enrollingsensors into the SimonXT and integrated security system and iscompatible with all existing GE Simon panels.

The integrated security system supports all pre-kitting functionalitydescribed in the installation process above. However, for the purpose ofthe following example, no kitting is used.

-   -   1. Order and Physical Install Process        -   a. Once an order is generated in the iControl system, an            account is created and an install ticket is created and sent            electronically to the security system provider for            assignment to an installer.        -   b. The assigned installer picks up his/her ticket(s) and            fills his/her truck with individual sensors, cameras, iHubs,            Simon XTs, etc. Optionally, the installer can also stock            homeplug adapters for problematic installations.        -   c. The installer arrives at the address on the ticket, and            analyzes the house and talks with the homeowner to determine            sensor locations. At this point assume the homeowner            requests three (3) cameras, five (5) door/window sensors,            one (1) glass break detector, one (1) smoke detector, and            one (1) keyfob.        -   d. Installer mounts SimonXT in the kitchen or other location            in the home. The installer routes a phone line to Simon XT            if available. GPRS and Phone numbers are pre-programmed in            SimonXT to point to the provider CMS.        -   e. Installer places gateway in home in the vicinity of a            router and cable modem, and installs an ethernet line from            gateway to the router, and plugs gateway into an electrical            outlet.    -   2. Associate and Enroll gateway into SimonXT        -   a. Installer uses either his/her own laptop plugged into            router, or homeowners computer to go to the integrated            security system web interface and log in with an installer            ID/pass.        -   b. Installer enters ticket number into admin interface, and            clicks ‘New Install’ button. Screen prompts installer to add            devices.        -   c. Installer types in ID of gateway, and it is associated            with the user's account.        -   d. Installer clicks ‘Add Device’ and adds the cameras to the            user's account (by typing in the camera ID/Serial #).        -   e. Installer clicks ‘Add SimonXT’. Instructions prompt            installer to put Simon XT into install mode, and add gateway            as a wireless keypad.        -   f. Installer goes to Simon XT and enters the installer code            into the Simon XT. Learns ‘gateway’ into the panel as a            wireless keypad as group 1 type sensor.        -   g. Installer returns to Web portal, and clicks the ‘Finished            Adding SimonXT’ button.        -   h. Gateway now is alerted to all subsequent installs over            the security system RF.    -   3. Enroll Sensors into SimonXT via iControl        -   a. Installer clicks ‘Add Simon XT Sensors’—Displays            instructions for adding sensors to Simon XT.        -   b. Installer goes to Simon XT and uses Simon XT install            process to add each sensor, assigning zone, name, group.            These assignments are recorded for later use.        -   c. The gateway automatically detects each sensor addition            and adds the new sensor to the integrated security system.        -   d. Installer exits install mode on the Simon XT, and returns            to the Web portal.        -   e. Installer clicks ‘Done Adding Devices’.        -   f. Installer enters zone/sensor naming from recorded notes            into integrated security system to associate sensors to            friendly names.        -   g. All sensor information for the account is pushed to the            iConnect server, and is available to propagate to CMS            automation software through the CMS API.    -   4. Place and Tests Sensors in Home        -   a. Installer physically mounts each sensor in its desired            location.        -   b. Installer physically mounts Wifi cameras in their            location and plugs into AC power. Optional fishing of low            voltage wire through wall to remove dangling wires. Camera            transformer is still plugged into outlet but wire is now            inside the wall.        -   c. Installer puts SimonXT into Test mode from the keypad.        -   d. Installer manually tests the operation of each sensor,            receiving an audible confirmation from SimonXT.        -   e. Installer exits test mode from the Simon XT keypad.        -   f. Installer returns to web interface and is prompted to            automatically set up cameras. After waiting for completion            cameras are now provisioned and operational.    -   5. Installer instructs customer on use of the Simon XT, and        shows customer how to log into the integrated security system        web and mobile portals. Customer creates a username/password at        this time.    -   6. Customer and Installer observe that all sensors/cameras are        green.    -   7. Installer instructs customer how to change Simon XT user code        from the keypad. Customer changes user code and stores in        SimonXT.    -   8. The first time the customer uses the web portal to Arm/Disarm        system the web interface prompts the customer for the user code,        which is then stored securely on the server. In the event the        user code is changed on the panel the web interface once again        prompts the customer.

The panel of an embodiment can be programmed remotely. The CMS pushesnew programming to SimonXT over a telephone or GPRS link. Optionally,iControl and GE provide a broadband link or coupling to the gateway andthen a link from the gateway to the Simon XT over GE RF.

In addition to the configurations described above, the gateway of anembodiment supports takeover configurations in which it is introduced oradded into a legacy security system. A description of example takeoverconfigurations follow in which the security system (FIG. 2 , element210) is a Dialog system and the WSP (FIG. 2 , element 211) is a GEConcord panel (e.g., equipped with POTS, GE RF, and Superbus 2000 RS485interface (in the case of a Lynx takeover the Simon XT is used)available from General Electric Security. The gateway (FIG. 2 , element220) in the takeover configurations is an iHub (e.g., equipped withbuilt-in 802.11b/g router, Ethernet Hub, GSM/GPRS card, RS485 interface,and iControl Honeywell-compatible RF card) available from iControlNetworks, Palo Alto, Calif. While components of particular manufacturersare used in this example, the embodiments are not limited to thesecomponents or to components from these vendors.

The security system can optionally include RF wireless sensors (e.g., GEwireless sensors utilizing the GE Dialog RF technology), IP cameras, aGE-iControl Touchscreen (the touchscreen is assumed to be an optionalcomponent in the configurations described herein, and is thus treatedseparately from the iHub; in systems in which the touchscreen is acomponent of the base security package, the integrated iScreen(available from iControl Networks, Palo Alto, Calif.) can be used tocombine iHub technology with the touchscreen in a single unit), andZ-Wave devices to name a few.

The takeover configurations described below assume takeover by a “new”system of an embodiment of a security system provided by another thirdparty vendor, referred to herein as an “original” or “legacy” system.Generally, the takeover begins with removal of the control panel andkeypad of the legacy system. A GE Concord panel is installed to replacethe control panel of the legacy system along with an iHub with GPRSModem. The legacy system sensors are then connected or wired to theConcord panel, and a GE keypad or touchscreen is installed to replacethe control panel of the legacy system. The iHub includes the iControlRF card, which is compatible with the legacy system. The iHub finds andmanages the wireless sensors of the legacy system, and learns thesensors into the Concord by emulating the corresponding GE sensors. TheiHub effectively acts as a relay for legacy wireless sensors.

Once takeover is complete, the new security system provides ahomogeneous system that removes the compromises inherent in taking overor replacing a legacy system. For example, the new system provides amodern touchscreen that may include additional functionality, newservices, and supports integration of sensors from variousmanufacturers. Furthermore, lower support costs can be realized becausecall centers, installers, etc. are only required to support onearchitecture. Additionally, there is minimal install cost because onlythe panel is required to be replaced as a result of the configurationflexibility offered by the iHub.

The system takeover configurations described below include but are notlimited to a dedicated wireless configuration, a dedicated wirelessconfiguration that includes a touchscreen, and a fished Ethernetconfiguration. Each of these configurations is described in detailbelow.

FIG. 78 is a block diagram of a security system in which the legacypanel is replaced with a GE Concord panel wirelessly coupled to an iHub,under an embodiment. All existing wired and RF sensors remain in place.The iHub is located near the Concord panel, and communicates with thepanel via the 802.11 link, but is not so limited. The iHub managescameras through a built-in 802.11 router. The iHub listens to theexisting RF HW sensors, and relays sensor information to the Concordpanel (emulating the equivalent GE sensor). The wired sensors of thelegacy system are connected to the wired zones on the control panel.

FIG. 79 is a block diagram of a security system in which the legacypanel is replaced with a GE Concord panel wirelessly coupled to an iHub,and a GE-iControl Touchscreen, under an embodiment. All existing wiredand RF sensors remain in place. The iHub is located near the Concordpanel, and communicates with the panel via the 802.11 link, but is notso limited. The iHub manages cameras through a built-in 802.11 router.The iHub listens to the existing RF HW sensors, and relays sensorinformation to the Concord panel (emulating the equivalent GE sensor).The wired sensors of the legacy system are connected to the wired zoneson the control panel.

The GE-iControl Touchscreen can be used with either of an 802.11connection or Ethernet connection with the iHub. Because the takeoverinvolves a GE Concord panel (or Simon XT), the touchscreen is always anoption. No extra wiring is required for the touchscreen as it can usethe 4-wire set from the replaced keypad of the legacy system. Thisprovides power, battery backup (through Concord), and data link (RS485Superbus 2000) between Concord and touchscreen. The touchscreen receivesits broadband connectivity through the dedicated 802.11 link to theiHub.

FIG. 80 is a block diagram of a security system in which the legacypanel is replaced with a GE Concord panel connected to an iHub via anEthernet coupling, under an embodiment. All existing wired and RFsensors remain in place. The iHub is located near the Concord panel, andwired to the panel using a 4-wire Superbus 2000 (RS485) interface, butis not so limited. The iHub manages cameras through a built-in 802.11router. The iHub listens to the existing RF HW sensors, and relayssensor information to the Concord panel (emulating the equivalent GEsensor). The wired sensors of the legacy system are connected to thewired zones on the control panel.

The takeover installation process is similar to the installation processdescribed above, except the control panel of the legacy system isreplaced; therefore, only the differences with the installationdescribed above are provided here. The takeover approach of anembodiment uses the existing RS485 control interfaces that GE Securityand iControl support with the iHub, touchscreen, and Concord panel. Withthese interfaces, the iHub is capable of automatically enrolling sensorsin the panel. The exception is the leverage of an iControl RF cardcompatible with legacy systems to ‘takeover’ existing RF sensors. Adescription of the takeover installation process follows.

During the installation process, the iHub uses an RF Takeover Card toautomatically extract all sensor IDs, zones, and names from the legacypanel. The installer removes connections at the legacy panel fromhardwired wired sensors and labels each with the zone. The installerpulls the legacy panel and replaces it with the GE Concord panel. Theinstaller also pulls the existing legacy keypad and replaces it witheither a GE keypad or a GE-iControl touchscreen. The installer connectslegacy hardwired sensors to appropriate wired zone (from labels) on theConcord. The installer connects the iHub to the local network andconnects the iHub RS485 interface to the Concord panel. The iHubautomatically ‘enrolls’ legacy RF sensors into the Concord panel as GEsensors (maps IDs), and pushes or otherwise propagates other informationgathered from HW panel (zone, name, group). The installer performs atest of all sensors back to CMS. In operation, the iHub relays legacysensor data to the Concord panel, emulating equivalent GE sensorbehavior and protocols.

The areas of the installation process particular to the legacy takeoverinclude how the iHub extracts sensor info from the legacy panel and howthe iHub automatically enrolls legacy RF sensors and populates Concordwith wired zone information. Each of these areas is described below.

In having the iHub extract sensor information from the legacy panel, theinstaller ‘enrolls’ iHub into the legacy panel as a wireless keypad (useinstall code and house ID—available from panel). The iHub legacy RFTakeover Card is a compatible legacy RF transceiver. The installer usesthe web portal to place iHub into ‘Takeover Mode’, and the web portalthe automatically instructs the iHub to begin extraction. The iHubqueries the panel over the RF link (to get all zone information for allsensors, wired and RF). The iHub then stores the legacy sensorinformation received during the queries on the iConnect server.

The iHub also automatically enrolls legacy RF sensors and populatesConcord with wired zone information. In so doing, the installer selects‘Enroll legacy Sensors into Concord’ (next step in ‘Takeover’ process onweb portal). The iHub automatically queries the iConnect server, anddownloads legacy sensor information previously extracted. The downloadedinformation includes an ID mapping from legacy ID to ‘spoofed’ GE ID.This mapping is stored on the server as part of the sensor information(e.g., the iConnect server knows that the sensor is a legacy sensoracting in GE mode). The iHub instructs Concord to go into install mode,and sends appropriate Superbus 2000 commands for sensor learning to thepanel. For each sensor, the ‘spoofed’ GE ID is loaded, and zone, name,and group are set based on information extracted from legacy panel. Uponcompletion, the iHub notifies the server, and the web portal is updatedto reflect next phase of Takeover (e.g., ‘Test Sensors’).

Sensors are tested in the same manner as described above. When a HWsensor is triggered, the signal is captured by the iHub legacy RFTakeover Card, translated to the equivalent GE RF sensor signal, andpushed to the panel as a sensor event on the SuperBus 2000 wires.

In support of remote programming of the panel, CMS pushes newprogramming to Concord over a phone line, or to the iConnect CMS/AlarmServer API, which in turn pushes the programming to the iHub. The iHubuses the Concord Superbus 2000 RS485 link to push the programming to theConcord panel.

FIG. 81 is a flow diagram for automatic takeover 2100 of a securitysystem, under an embodiment. Automatic takeover includes establishing2102 a wireless coupling between a takeover component running under aprocessor and a first controller of a security system installed at afirst location. The security system includes some number of securitysystem components coupled to the first controller. The automatictakeover includes automatically extracting 2104 security data of thesecurity system from the first controller via the takeover component.The automatic takeover includes automatically transferring 2106 thesecurity data to a second controller and controlling loading of thesecurity data into the second controller. The second controller iscoupled to the security system components and replaces the firstcontroller.

FIG. 82 is a flow diagram for automatic takeover 2200 of a securitysystem, under an alternative embodiment. Automatic takeover includesautomatically forming 2202 a security network at a first location byestablishing a wireless coupling between a security system and agateway. The gateway of an embodiment includes a takeover component. Thesecurity system of an embodiment includes security system components.The automatic takeover includes automatically extracting 2204 securitydata of the security system from a first controller of the securitysystem. The automatic takeover includes automatically transferring 2206the security data to a second controller. The second controller of anembodiment is coupled to the security system components and replaces thefirst controller.

Home View as described herein enables users to quickly access and viewstate, and control devices from a single user experience. Home Viewprovides an easy way for users to represent each floor of their home andindicate the location of security sensors, cameras, lights, thermostats,locks, and any other devices in the home automation system. Using thisinterface, users can easily check on the state of their home fromanywhere using a mobile phone or web browser. To further enhance the“glanceable” experience of home management, the Home View of anembodiment includes a three-dimensional version referred to herein as“Home View 3D”. Home View 3D provides the added ability to see alllocations in a multi-floor dwelling at once. For example, a user caninstantly notice an open window upstairs, turn off a light, viewtemperature on each floor, and access cameras outside with a singleclick, to name a few.

FIG. 83 is an example status interface of Home View 3D, under anembodiment. FIG. 84 is an example user interface of Home View 3D, underan embodiment.

To enable Home View 3D, the user can edit the representation of theirhome using one or more of a web browser, smart phone, and tabletcomputer, and select or click the Home View 3D option. That setting issaved in the cloud-based environment or other server environment, andchanges the user's web and mobile devices to use a 3D view. Home View 3Dprovides unique and powerful visualization of the home lets the userfeel connected and in control of their home from anywhere in the world.FIG. 85 is an example user interface showing “enable” control of HomeView 3D, under an embodiment.

Home View 3D is disabled by default, and a user can enable it in anyeditor of an embodiment. Home View 3D includes options in the editormenu to toggle the 3D option. These settings affect or are applied toall client devices that interface with the site (e.g., after next login,depending on caching). FIG. 86 is an example user interface showing“disable” control of Home View 3D, under an embodiment.

Additionally, when Home View 3D is enabled, the editor displays anindicator to that effect using the thumbnails, but the embodiment is notso limited. FIG. 87 is an example editor interface with indicators ofHome View 3D being enabled, under an embodiment.

The 3D of an embodiment is a render-time feature, but is not so limited.The interaction with Home View 3D is as described in detail herein witha single-floor rendering (e.g., devices include popups indicating state,double-clicking devices causes navigation, etc.). In Home View 3D of anembodiment, if the canvas is non-square, the rendering stretches to fitthe canvas (or display viewer). For example, on tablets the renderer canbe wider than it is tall. Additionally, floating text for devices at thetop edge of lower floors flips over to render below the device, just asthey did for the 2D renderer described herein.

Regarding general rendering and scaling rules of an embodiment, HomeView 3D primarily affects walls with isometric skewing to make them looktipped back. As an example, the front wall is full width, and the backwall is approximately 80% of normal width, giving the illusion of depth.Devices and text are not skewed and the device or text appears as ifsitting upright on the tipped floors. Devices and text of an embodimentare scaled to match horizontal scaling. Specifically, devices and texton the front edge are approximately 100% normal size, and devices andtext on the back edge are approximately 80% of normal size.

Furthermore, floors are tapered so that a top floor is slightly widerthan the bottom floor to add to the 3D illusion. Specifically, the frontcorners of the bottom floor render as they would in 2D (e.g., with agutter on left/right), but the front corners of the top floor isapproximately one pixel away from canvas edge, but the embodiment is notso limited.

Home view 3D of an example embodiment supports between one and fivefloors, but is not so limited. FIG. 88 is an example user interfaceshowing five floors, under an embodiment.

Home View 3D includes customization and branding but is not so limited.FIG. 89 is an example interface of Home View 3D showing variables, underan embodiment. Home View branding variables are as follows, but are notso limited:

A. threeDScaleBackRowByPct  = 0.8; //horizontally scale back wall (andicons and text) this %, 80% width of front edge B.threeDVertScaleSingleFloorPct = 0.75; //if rending single floor 3D,scale vertically by this percent C. threeDVertFloorGapInTiles = 1.2;//insert vertical gap betwen floors, height is this many tiles D.threeDTopFloorColorStops = [{stop: 0, color: “rgb(180,180,180)”},//color for back edge of top floor E.   {stop: 1, color:“rgb(180,180,180)”} ]; //color for front edge of top floor F.threeDBotFloorColorStops = [{stop: 0, color: “rgb(180,180,180)”},//color for back edge of shadow on lower floors G.   {stop: 0.75, color:“rgb(180,180,180)”}, //color for front edge of shadow on lower floors H.  {stop: 0.9, color: “rgb(180,180,180)”}, //color for back edge oflighted section of lower floors I.   {stop: 1 , color:“rgb(180,180,180)”} ]; //color for front edge of lighted section oflower floors J. threeDSubShadowGapInTiles  = 2.5; //gap between bottomfloor and sub-shadow; height is this many tiles K. threeDSubShadowColor= “rgba(0,0,0,0.15)”; //color and transparency of shadow (same shape asbottom floor) L. threeDSubShadowBlur = 20; //radius of blur forsub-shadow

Home View 3D presents more information when a device (e.g., tablet,phone, touch screen, etc.) is in landscape mode. When 3D is enabled andthe host device is in landscape mode, the rendering of an embodiment isapproximately 40% wider than it is tall, but the embodiment is not solimited. Further, it should also center both vertically andhorizontally. FIG. 90 shows example renderings for square, wide, andtall canvases, 3D single-floor premises, and 3D multi-floor premises,under an embodiment.

In addition to rendering 3D, Home View 3D includes historical activitydata or information for sensors, like a “heat map” for history thatfades with time. For example, if a door opens or closes, the device iconwill have a bright glow around it that will fade with time. At a glancethe user can tell where there has been recent activity. FIG. 91 is anexample user interface showing a “heat map” of Home View 3D, under anembodiment. In this example, sensors in the “family room” and “livingroom” are displayed with a bright glow indicating recent activity, thebut embodiment is not so limited.

This feature is activated on each client when the user selects or tapsthe history icon and enables history view by choosing a time period.Once a time period is selected, that client shows a history glow for allsensors that have had activity within that time period. For example,with 1 Week selected, a sensor that has been tripped today will have astrong glow, a sensor tripped 3 days ago will be half faded, a sensortripped 6 days ago will have a very faint glow, and a sensor tripped 7days ago (or more) will have no glow at all.

The heat map feature includes three UI elements but is not so limited.An icon is used to enable and set the feature. By default, the icon is astandard history icon (clock in circle). But if history view is enabled,the circle contains the time period shown (10M=10 minutes, 1D=10 daysetc.). Additionally, a popup dialog enables the user to enable thefeature and select a time period. A glow ring is shown around sensors,and the glow ring is configured to fade with passage of time. FIG. 92 isan example user interface for configuring a “heat map” of Home View 3D,under an embodiment. FIG. 93 is another example user interface forconfiguring a “heat map” of Home View 3D, under an embodiment.

Embodiments display activity for the premises devices based on the typeof device, but are not so limited. For example, activity presented forsensors includes a last update for any point in the instance (e.g.,open/close, low battery, trouble, tamper, bypass, alarms, etc.).Activity presented for door locks and garage door controllers includes alast or most recent update for any point in the instance (e.g.,open/close, lock/unlock, low battery, trouble, etc.). Activity presentedfor lights (w/o energy) includes last or most recent update for anypoint in the instance (e.g., on/off, dimmer level changes, offline,etc.). Activity presented for lights that report energy includes last ormost recent update for any point in the instance (e.g., on/off, dimmerlevel changes, offline, etc.) (energy changes and related points may beignored). Activity presented for thermostats includes last or mostrecent update for any point in the instance (e.g. heating/cooling,setpoint changes, mode changes, low battery, etc.). Activity presentedfor cameras includes last or most recent update for motion sensor (maynot report camera taking pictures/clips). Activity presented for energymay not include report activity.

When computing coordinates in two dimensions (2D), an embodiment used atwo-dimensional array (28×28) comprising information about each “tile”in the data grid for each floor. Here, a block of numbers from theserial data is provided to draw a large rectangle of floor tiles:

 for (i=0; i<tilesArr.length; i++) {   if (tilesArr[i].length > 4) {   x = (tilesArr[i][1]);    y = (tilesArr[i][2]);    w =(tilesArr[i][3]);    h = (tilesArr[i][4]);    //save individual tiledata for editing    for (row=y; row < (y+h) && row<this.numTiles; row++){     for (col=x; col < (x+w) && col<this.numTiles; col++)this.t[row][col].shown=true; //turn on tile for each value in vector   }    //remember full tile blocks, ONLY for superfast rendering (notedit mode, where segs are being changed constantly)    point0 =this.pSkewXY( x *this.tileWidth + this.startPosX, y *this.tileWidth +this.startPosY);    point1 = this.pSkewXY((x + w)*this.tileWidth +this.startPosX, y *this.tileWidth + this.startPosY);    point2 =this.pSkewXY((x + w)*this.tileWidth + this.startPosX, (y +h)*this.tileWidth + this.startPosY);    point3 = this.pSkewXY( x*this.tileWidth + this.startPosX, (y + h)*this.tileWidth +this.startPosY);    this.tFastRender.push([point0, point1, point2,point3]);   }  }

For example, if the data included taadc, that becomes an array[0,0,3,2], meaning draw a rectangle from the origin, three tiles wideand two tiles high. The above code, computes the true pixel position forthose locations, converting the parameters to 4 (x,y) corners of therectangle to render:

-   -   . . . =>.point0.point1=>.(x0,y0).(x1,y1)        -   . . . . point3.point2.(x3,y3).(x2,y2)

The actual pixel location of each x,y coordinate is taking the abstractgrid location and turning it into pixels. Each location is multiplied bythe tileWidth, then offset by the rendering start positions startPosXand startPosY that account for gutters. To compute an abstract positionlike (3,2), the params are multiplied by the pixel width of a tile, andoffset by the pixel position startPosX etc.

pixelPosition for (x,y)=(x*this.tileWidth+this.startPosX,y*this.tileWidth+this.startPosY)

For 2D rendering, the pSkewXY function does not alter these pixelpositions, but returns them. For 3D rendering, each x,y position getsaltered in several ways as follows, but the embodiment is not solimited:

-   -   1. If there are multiple floors, each y position is scaled        vertically (for example, if there are 2 floors, every y value is        divided by 2). The first floor would be drawn from the origin,        but the 2nd floor would also be offset vertically so it draws        halfway down. In addition, vertical offset is altered to provide        a gap is between floors.    -   2. If there is a single floor, each position is scaled        vertically to 60% of its height and offset to be vertically        centered. This is controlled by a ppref.    -   3. All x positions are altered by shifting them toward the        vertical midline. For example, in a 100 px canvas, An x value of        50 it is unchanged. However, if x is 0, it needs to be skewed        20% toward the center. Since the back row is to be scaled to 80%        width, we bring X to 80% of it's distance from the vertical        midline. In this example, x would change to (50−abs(x−50)*0.8).        So an x at 0 shifted 20% to midline becomes x=10. This effect is        reduced as we render lower rows (toward the front edge of the        floor). Back row is squeezed to 80%, and front row is not        horizontally squeezed at all, so 100% of original position.    -   4. A front-to-back scaling factor must be computed for later        shrinking of device icons and label text. Devices in back (top)        row are scaled to 80%, halfway back 90%, and front edge (bottom)        devices are 100%.

An example follows of the core skewing algorithm of an embodiment, incode, but the embodiment is not so limited:

//------------------------------------------------------------  //pSkewXY  // arguments: absolute canvas x and y positions  // return:object with x and y properties with new, skewed values  //  // Ingeneral, y skew is scaled by # floors (2 floors means y = y/2). X skewis more subtle.  // If x is about halfway across, its unaffected. And ifY is the max, x is the front row and  // undaffected. But the farther“back” you go, the more skewed x is. For example, in the first  // row,x==0 will be bent in by the 80% factor, or 10% increased towards themiddle.  //------------------------------------------------------------ ic_hvwFloorData.prototype.pSkewXY = function (px, py) {   var devScale= 1; //computed amount to scale devices for each location. 1 for frontedge (bottom row), .80 for back edge (top row)   try {    if(this.render3D) { //skewing ONLY affects render mode, not editor     if(!this.cache) { //to ensure this is fast, precompute everythingpossible, only once per floor      var scaleBackRowByPct=this.threeDScaleBackRowByPct,   //horizontally scale back wall (andicons and text) this %       vertScaleSingleFloorPct =this.threeDVertScaleSingleFloorPct, //if rending single floor 3D, scalevert by this %       floorGapInTiles = this.threeDVertFloorGapInTiles,//vert gap btwn floors, height is this many tiles (scaled by # floors)      gapBetweenFloors = (this.numFloors>1)?(floorGapInTiles*this.tileHeight/(this.numFloors)) : 0; //gap in pixelsif 3D & >1 flr      this.cache = { }; //create or clear cache object     this.cache.xSkewFactor = (1-scaleBackRowByPct); //constant controlsamount of skew, such as .8 = 80% horiz scale     this.cache.ySkewFactor = (1 - (this.numFloors-1)*(floorGapInTiles/this.numTiles)) / this.numFloors;     this.cache.drawWidth   = this.tileWidth * this.numTiles;     this.cache.drawHeight  = this.tileHeight * this.numTiles;     this.cache.yOffset  = ((this.numFloors - 1) - this.floorNum) *//amount to shift each floor down        ((this.cache.drawHeight/this.numFloors) + gapBetweenFloors);//offset by # floors + gap      if (this.numFloors == 1) {  //if singlefloor       this.cache.ySkewFactor *= vertScaleSingleFloorPct;   //scale vertically       this.cache.yOffset = ((1 -vertScaleSingleFloorPct) / 2) * this.cache.drawHeight; //and offsetvertically so centered      }      this.cache.halfDrawWidth  =this.cache.drawWidth / 2; //precompute for speed     this.cache.xSkewMultiplier = this.cache.drawHeight *(this.cache.xSkewFactor) / 2;      this.cache.yScaleFactor  =(1-(this.cache.xSkewFactor)*(this.cache.drawHeight -this.startPosY)/(this.cache.drawHeight));     }     //compute skewed x,y positions, and scale for this row     devScale =py*this.cache.xSkewFactor/this.cache.drawHeight +this.cache.yScaleFactor; //device scale: compute before altering py    px  += (1 - (px-this.startPosX)/this.cache.halfDrawWidth) * //addnormal X factor skewing        (1 -(py-this.startPosY)/this.cache.drawHeight )* //but diminished by Yfactor        this.cache.xSkewMultiplier; //then scale overall     py  =(py-this.startPosY)*this.cache.ySkewFactor + this.startPosY +this.cache.yOffset; //remove start pos, skew, then add back    }   }  catch (ev) {    //console.log(“Home View: pSkew failed ”+ev);   }  return {x:px, y:py, scaleFor3D:devScale};  };

Tapering of the floors in Home View 3D, as described in detail herein,means that the top floor is rendered slightly wider than the bottomfloor. Since the render naturally has vertical gutters on the left andright edge, and these gutters are wider than needed since the floors areskewed and smaller, the algorithm of an embodiment renders the bottomfloor with gutter unchanged, and reduces the top floor gutter toapproximately 35% of its normal width, as an example.

Before computing all the locations for rendering a floor, an embodimentshrinks this gutter for the higher floors. For example, with 3 floors,the gutters are approximately 35%, 57%, and 100% of their typical width,but are not so limited. Since the gutters are smaller, the floors arewider, so an embodiment grows the tile widths by that same approximatepercent. An example algorithm is as follows, but is not so limited:

if (render3D) { //This block makes the higher floors a bit wider thentapers inward to enhance 3D illusion   this.cache = null; //need toclear pre-computed cache from lower floors   var gutterPct = 0.35 +0.65*((numFloors-1)-floorNum)/((numFloors>1)?(numFloors- 1):1); //topfloor: 35% gutter, bottom floor: 100% gutter   this.startPosX *=gutterPct; //shrink startPosX that % to shift closer to edge  this.tileWidth *= 1 +(2*(startPosX-this.startPosX)/(this.numTiles*this.tileWidth)) //growtileWidth by same percent gutter shrank  }

Embodiments of the integrated system described herein include a userinterface (UI) that is a cross-platform UI providing control over homeautomation and security systems and devices from client devicesincluding but not limited to tablets, smart phones, iOS devices, andAndroid devices. The user interface, also referred to herein as “Alta”,includes Home View, which as described in detail herein and in theRelated Applications provides a top-level view in which premises devicesare displayed according to their actual position in the premises.

FIG. 94 is an example UI screen, under an embodiment. Using the UI,devices are displayed in Home View, List View, and Details View. HomeView comprises a top-level view in which premises devices are displayedaccording to their actual position in the premises. Tap on a device iconin Home View to view an overlay for quick access to details and controls(when applicable) for that device.

The Tab Bar, located at the bottom of the screen in an exampleembodiment, provides navigation through the app. A tap detected on adevice group's icon in the Tab Bar navigates to a Details View page ofeither the last viewed device in that group, or otherwise the firstlisted device in the group.

Details View displays information and controls for a device. Swipe leftor right to move between devices. Details View displays information andcontrols for a device; this view does not exist for Sensors. Swipe leftor right to move between devices.

The List icon to the right of the device name in Details View pulls upthe device list for the current group (e.g., if previously viewing athermostat, a list of installed thermostats is displayed). This ListView appears over the content area in a vertically scrolling list. Viewa device's details by tapping on that device in the list to view it inDevice View. Tap the X icon to the right of the list header to close thelist and return to the previously-viewed device.

The navigation layers appear in the UI, from top to bottom for example,as follows: Full-Screen View and Status Bar (with mini system icon);Modal dialogs and Menus; Warnings/Messages and Status Bar (no minisystem icon)/System Bars; History View; Tab Bar; List View; Detail Viewand Home View; Background.

FIG. 95 shows an example Status Bar of the UI, under an embodiment. TheStatus Bar of an example includes the following elements: System statustext (e.g., “Disarmed), and Sensor status text (e.g., “All Quiet”).

FIG. 96 shows an example System Bar of the UI, under an embodiment. TheSystem Bar of an embodiment includes but is not limited to the followingelements: Mode Button (shows current mode); System Icon (reflectscurrent arm status by color, also shows badging for tripped sensors andsystem trouble); and Arm/Disarm Button (shows arm/disarm action). TheSystem Bar shows current Mode and Arm status and allows security panelarm and disarm options and mode changes. Tap the Arm button to selectarming options. Tap the Disarm button to disarm. Tap the Mode button toselect a new mode. Press the system icon as a shortcut to the sensorslist.

FIG. 97 shows an example Tab Bar of the UI, under an embodiment. The TabBar of an example provides navigation to each section in the app, and ispinned to the bottom of the screen and displayed on top of the contentarea, but is not so limited. The current section is highlighted. Thetouch area for each tab is larger than the icon. Sections marked with anasterisk (*) are shown only if devices in that group are installed:List; Home (Home View/Sensors: HV shown first if set up, and Sensorsotherwise); Cameras*; Lights*; Thermostats*; Doors*; Energy*; andSettings. When sensors (in Home), cameras, or any lifestyle device groupinclude at least one trouble state like offline, unknown or installing,a trouble badge appears on the top right corner of the icon.

The UI of an embodiment includes content area positioned under theSystem Bar. When scrolling vertically, content scrolls under the Tab Barat the bottom and under the System Bar and Status Bar at the top. Thecontent area includes information about devices or other systeminformation in several ways. Home View is a visual arrangement ofsecurity and lifestyle devices on a floor plan. Details View is adetailed device screen that fills the content area and can also bescrolled horizontally to move between devices. List View is a verticallyscrolling list displayed in a sheet. Scroll horizontally to move betweendevice groups. In Full Screen mode, the content area is the entire areabeneath the Status Bar. The type of content displayed in the contentarea in Full Screen mode includes: live video; captured clips; capturedpictures; third party content (widgets); and installer application.

FIG. 98 shows an example Details View of the UI, under an embodiment.Details View displays information and controls for a device (or othertypes of information such as settings or widget icons). Device detailsappear when tapping a device icon in Home View (swipe navigationdisabled, no list icon, appears in a dark dialog box), tapping the tabicon for a device group (horizontal swiping enabled, list icon, floatsin content area), or tapping a device from list view (horizontal swipingenabled, list icon, floats in content area). Tap the List icon to see alist of devices in the current device section.

On Home View, device details are presented in a card overlay. FIG. 99shows two versions of an example Details Card in Home View of the UI,under an embodiment.

FIG. 100 shows an example List View of the UI, under an embodiment. FIG.101 shows an example List layout of List View of the UI, under anembodiment. List View is a compact display of items in a verticallyscrolling list. For lifestyle devices, List View is accessible bytapping the List icon in Details View. When a list is displayed, tap onthe List icon to hide the list. The list is dismissed and the viewreturned to the previous view, as if the X icon was tapped. When viewingHome View, tap on the List icon to navigate to the Sensors list. If HomeView is toggled off, the Sensors list becomes the default view whentapping on the Home icon. The types of information that may be displayedin a List View include sensors, cameras, lights, thermostats, doors, andenergy, but embodiments are not so limited.

FIG. 102 shows a device list item of the UI, under an embodiment. Eachdevice list item includes but is not limited to the following: Icon(indicates device type and status, vertically-centered, left-aligned);Name (bold text, left-aligned) in either portrait (listed on first row)or landscape (listed inline, left-aligned); Zone number (sensors only,normal text) in either portrait (listed on second row, left-aligned) orlandscape (Inline, left-aligned following the device name); and Statustext (sensor and device lists only, normal text, includes othersecondary status such as “Stopped” or “Low battery”) in either portrait(vertically centered, right-aligned) or landscape (Inline,right-aligned). Tap an item in List View to close the list and see theDetail View for the selected item. In Settings, this may navigate toanother List View menu.

FIG. 103 shows an example Settings Menu of the UI, under an embodiment.Menus of an embodiment include the same structure as lists, but may nothave icons. These also cover the rest of the UI when they are displayed,though maintains the same width as a list in landscape, and can beclosed by tapping the X icon at the top right of the header. Menusfollow the same vertical scroll behavior as lists.

FIG. 104 shows an example Events History View of the UI, under anembodiment. Event history views or lists scroll vertically under theheader. Events are organized under Date headers and listed in reversechronological order (with the most recent event at the top). The topheader is pinned to the top and the entries for that day scroll underthe date header, but the next header pushes the previous header underthe sheet header and then is pinned until the next header pushes itaway. Individual entries are time-stamped. Sensors, Cameras, and NotableEvents present history as a list of events. Each sensor and camera hasits own history, while Notable Events is a single history sheet.

History View is used when viewing a list of recent or past events for asystem or device. These sheets slide up from the bottom and, whendismissed by tapping the X icon, slide down to reveal the UI underneath.The header includes the device name and an ‘X’ button to close thehistory view and return to the previous view. Side-swipe navigation isdisabled in this view. History View may present history as a scrollinglist of events or as a history graph.

The UI of an embodiment includes line graphs, but is not so limited.FIG. 105 shows example thermostat line graphs of the UI, under anembodiment. Thermostats (using line graphs) and Energy devices (usingbar graphs) present history in graph form for each device.

System warnings and messages appear in a message bar, which ispositioned beneath the System Bar in an embodiment. FIG. 106 showsexample versions of a dismissable message in a message bar of the UI,under an embodiment. FIG. 107 shows example versions of anon-dismissable message in a message bar of the UI, under an embodiment.

The Message Bar appears whenever a message needs to be shown, regardlessof context, except when in full-screen mode (third party apps,full-screen video or device manager for example). Two levels of messageurgency are handled by the message bar, which include Info (grey) andWarning (yellow/red text/red icon). Messages may be hidden or dismissedas indicated by the icon on the right side of the message: Dismissable(has a “dismiss” X icon, and optionally a timeout); or Non-dismissable(“hide” icon, no timeout). Warning messages also add the appropriatebadge to the System Icon.

Messages stack up as they accumulate until they are hidden or dismissed.They are displayed in chronological order, but sorted with warningsgrouped at the top and information messages in a group below warnings.FIG. 108 shows example versions of multiple messages presented by theUI, under an embodiment.

Dismissable messages with a timeout value are automatically hidden whenthey expire. Otherwise, messages are individually dismissed or hidden.If the message is dismissable, tapping the dismiss icon dismisses themessage permanently. If the message is non-dismissable, tapping the hideicon hides the message temporarily. When a non-dismissable message ishidden, the system icon badge bounces to reinforce the connection andserves as a reminder of where to find the message again.

To show hidden (non-dismissable) messages again, tap the system icon.The sensor list is shown and the non-dismissable messages are shownagain.

Upon completing sign-in procedures via the UI, the Home section isloaded and includes both Home View and the Sensors list. If Home View isset up, the app defaults to Home View after the app is launched. Onsites without Home View set up, the app defaults to the Sensors list onlaunch and the page dots are hidden. Page dots in this tab indicate HomeView and the Sensors list. The Home tab icon displays the trouble badgebased on the status of the sensors, not on the status of Home View. FromHome View, swipe right to left to go to the Sensors list. From theSensors list, swipe left to right to go to Home View.

FIG. 109 shows example versions of a Home View (3D, multiple floors)screen or page of the UI, under an embodiment. Home View allows users toview all installed premises devices at a glance. FIG. 110 shows anexample Home View (2D, multiple floors) screen or page of the UI, underan embodiment.

FIG. 111 shows an example Home View device control screen or page of theUI, under an embodiment. Tap on a device to show its details in a cardoverlay on top of Home View. Cameras will open the live video window.

FIG. 112 shows an example Notable Events screen or page of the UI, underan embodiment. Tap on the History icon to view Notable Events. If a sitehas more than one floor and Home View is in 2D mode, switching betweenfloors is handled by the Home View component: tap on a floor thumbnailto the right of the floor plan to navigate to a new floor.

FIG. 113 shows example versions of a sensor list screen or page of theUI, under an embodiment. Users without Home View enabled will see theSensors list with the site name visible when navigating to the Home tab.This also becomes the default view when loading into the app as long asHome View is disabled. Each device list item includes but is not limitedto the following: Icon (indicates device type and status,vertically-centered, left-aligned); Name (bold text, left-aligned.)either portrait (listed on first row) or landscape (listed inline,left-aligned); Zone # (sensors only, normal text) either portrait(listed on second row, left-aligned) or landscape (inline, left-alignedfollowing the device name); and status text (sensor and device listsonly, normal text, includes other secondary status such as “Stopped” or“Low battery”) either portrait (vertically centered, right-aligned) orlandscape (inline, right-aligned). Tap on a sensor in the list to viewthat sensor's history.

FIG. 114 shows an example Sensor History screens or pages of the UI,under an embodiment. The Sensor History screen includes history for theselected sensor, as well as controls (e.g. Bypass) for the sensor whereapplicable. This history sheet can appear by tapping an icon in HomeView (scrolling disabled) or tapping on a sensor in List View (scrollingenabled, swiping shortcut between sheets enabled). Sensor Historydisplays recent (since last reboot) activity for that sensor in ascrolling list.

FIG. 115 shows an example of arm options presented by the UI, under anembodiment. Press the Arm button to show the arm options dialog. Pressthe Arm button to show the arm options dialog. FIG. 116 shows an exampleof arm protest presented by the UI, under an embodiment. Arm protest isshown if some sensors are open or troubled while attempting to arm. Alist of sensors is shown. FIG. 117 shows an example of arm protestfailed presented by the UI, under an embodiment.

In the event of an alarm, the alarm dialog is shown. FIG. 118 shows anexample of arm dialogue presented by the UI, under an embodiment.

FIG. 119 shows an example of modes dialog presented by the UI, under anembodiment. The Modes button uses the name of the current mode for itslabel, or the partner-specified feature name otherwise. Press the Modesbutton to show a dialog including a list of modes. Select a mode tochange the mode on the site and close the dialog or tap on the X icon toclose the dialog without changing the mode.

FIG. 120 shows examples of camera detail screens presented by the UI,under an embodiment. Tap on the Cameras tab to see the first camera fromthe list in Details View. A recent thumbnail from the camera (scaled tofit) is displayed with a Play icon in the center. Tap on the image toview a full-screen landscape Live Video stream for the camera. If thecamera is offline, the last available picture is displayed if available,or a gray placeholder box and the Play icon is replaced with text thatreads “Offline”. On sites having multiple cameras, swipe left or rightto navigate between cameras. A History icon navigates to a list of videoclips and pictures recorded from the camera. A List icon navigates to aList View of installed cameras.

From the Details View, a tap on the List icon results in presentation ofthe Cameras list. FIG. 121 shows example camera device lists presentedby the UI, under an embodiment. Cameras with exceptional states havestatus text, though all cameras display status through their statusicon. Tap on a camera in the list to see the Details View for thatcamera. Tap on the X to return to the Details View for the last-viewedcamera.

FIG. 122 shows an example of camera full-screen live video presented bythe UI, under an embodiment. FIG. 123 shows camera capture options(e.g., “Take Picture”, “Take Video Clip”, etc.) presented by the UI,under an embodiment. FIG. 124 shows a capture message (e.g., “CapturingVideo Clip . . . ”) presented by the UI, under an embodiment. Tapanywhere while viewing Live Video to bring up the Video Timeline, aswell as a Capture button to capture clips or pictures and an X icon toclose and return to the Details View of the current camera (alsopossible with the OS back button). Tap on a Capture button to presentthe following options: Take Picture (take a picture on the currentcamera and see the following message: “Your picture will be taken in afew seconds.”) or Capture Video Clip (capture a video clip on thecurrent camera and see the following message: “Your video capture willbegin in a few seconds.”). The message is displayed in an overlay for acouple seconds and then disappears.

FIG. 125 shows example camera history (clips and pictures) viewspresented by the UI, under an embodiment. Tap the History icon on theDetails View of a camera to see history for that camera. Video clips andpictures are displayed together in a scrolling thumbnail grid list, andare sorted under Date headers (same as Sensor History). As a result, thetimestamp under the photo now only displays the time when captured, notthe date. Tap on a thumbnail to see the selected clip or picture infull-screen view.

Embodiments also include support for various types of switches. Moreparticularly, four types of switches are supported but embodiments arenot so limited: ON/OFF functionality; ON/OFF functionality in additionto a variable dimming control options; ON/OFF functionality with EnergyMonitor (Multifunction Device); and ON/OFF functionality in addition toa variable dimming control options with Energy Monitor (MultifunctionDevice).

FIG. 126A shows an example binary switch icon (“off” state) presented bythe UI, under an embodiment. FIG. 126B shows an example binary switchicon (“on” state, indicated by different color than “off” state)presented by the UI, under an embodiment.

FIG. 127A shows an example UI page with a binary switch (e.g., coffeemaker, etc.) icon (“off” state) presented by the UI, under anembodiment. FIG. 127B shows an example UI page with a binary switch(e.g., coffee maker, etc.) icon (“on” state, indicated by differentcolor than “off” state) presented by the UI, under an embodiment.

FIG. 128A shows an example dimmer switch icon (“off” state) presented bythe UI, under an embodiment. FIG. 128B shows an example dimmer switchicon (“on” state, indicated by different color than “off” state)presented by the UI, under an embodiment. FIG. 128C shows an exampledimmer switch icon (in use) presented by the UI, under an embodiment.Regarding dimmer interaction, “Tap” is tapping in the center to turn thedevice on/off. Tap on the dimmer track to jump to the closest point onthe track. “Drag” is dragging along the dimmer track should jump to thefinger location, and then follow the finger location at a pre-specifiedratio (e.g., 1:1, etc.).

FIG. 129A shows an example UI page with a dimmer switch (e.g., light,etc.) icon “off” state) presented by the UI, under an embodiment. FIG.129B shows an example UI page with a dimmer switch (e.g., light, etc.)icon (“on” state, indicated by different color than “off” state)presented by the UI, under an embodiment.

Additionally, embodiments include support for thermostats. FIGS. 130Aand 130B show example thermostat state icons presented by the UI, underan embodiment. The thermostat state icons include, but are not limitedto, auto mode cooling, auto mode heating, cool mode cooling, heat modeheating, fan not supported, auto mode (not heating/cooling), off, andoffline. The thermostat control includes: current temperature; heatingand cooling set point indicators; heating and cooling visual indicator;thermostat mode button (tap to display); and fan mode button (tap todisplay). Thermostats can have the following combinations of featuresbut are not so limited: heat, cool and off thermostat modes; heat, cool,off and automatic thermostat modes; heat, cool and off thermostat modesplus on, auto fan modes; and heat, cool, off and auto thermostat modesplus on, auto fan modes.

FIG. 131 shows set point drag and tap areas of a thermostat presented bythe UI, under an embodiment. “Tap” is tapping anywhere within the fourquadrants of the control to change the set point in increments (e.g.,one degree, etc.), as indicated by the +/−icons. “Drag” is draggingalong either set point track should jump to the finger location (dragonly, not tap), and then follow the finger location at a ratio (e.g.,1:1 ratio, etc.).

FIG. 132 shows the thermostat set point (heat/cool) slider in use (top),and increment/decrement function in use (bottom) as presented by the UI,under an embodiment. When the thermostat is actively heating, theheating indicator (center glow) and “Heating” label are shown. When thethermostat is actively cooling, the cooling indicator (center glow) and“Cooling” label are shown. When the thermostat is off, the temperaturecontrols are hidden.

FIG. 133A shows example versions of thermostat details (auto mode)screens presented by the UI, under an embodiment. FIG. 133B shows anexample thermostat (actively heating) screen presented by the UI, underan embodiment. FIG. 133C shows an example thermostat (actively cooling)screen presented by the UI, under an embodiment. FIG. 133D shows anexample thermostat (changing cool setpoint) screen presented by the UI,under an embodiment. FIG. 133E shows an example thermostat (off) screenpresented by the UI, under an embodiment.

Embodiments include a tap-to-popup UI for operation mode (Mode) and fanmode (fan icon). FIG. 134 shows mode selection popups presented by theUI, under an embodiment. Tapping Mode or fan icon shows a popup withmode selector+X icon to close.

Furthermore, embodiments include support for various types of doorlocks. FIG. 135 shows an example door lock control tap and drag controlscreen presented by the UI, under an embodiment. The door lock andgarage door controls include current state (e.g., open, closed, locked,unlocked) and lock ring with drag handle.

FIG. 136 shows example lock icons (e.g., locked state, unlocked state,low battery) presented by the UI, under an embodiment. To lock or unlockthe door, drag up, down, radially or diagonally within the upper-leftportion of the control. The handle will not stay in a position otherthan 0° or 90°, but is not so limited. For example, the handle can bedragged to any location between 0° and 90° but on release, the handlewill reset to the nearest position. Tap the center lock icon to togglebetween locked/unlocked or open/closed.

FIG. 137A shows an example UI with door lock details icon (inactive)presented by the UI, under an embodiment. FIG. 137B shows an example UIpage with door lock details icon (active) presented by the UI, under anembodiment.

FIG. 138A shows an example UI page with garage door details icon(inactive) presented by the UI, under an embodiment. FIG. 138B shows anexample UI page with garage door details icon (active) presented by theUI, under an embodiment.

Embodiments also include support for various types of energy meters ordevices. FIG. 139 shows an example energy meter details page of the UI,under an embodiment. Energy devices show current power usage on asemi-logarithmic scale but are not so limited.

Embodiments include a system comprising an automation network comprisinga gateway at a premises. The gateway is coupled to a remote network. Thegateway is configured to control a plurality of components at thepremises including at least one of a thermostat and a lock. The systemincludes a sensor user interface (SUI) coupled to the gateway andpresented to a user via a plurality of remote client devices. The SUIincludes a plurality of display elements for managing and receiving dataof the plurality of components agnostically across the plurality ofremote client devices. The plurality of display elements includes aninteractive icon comprising a plurality of control regions. Each controlregion is configured to control a state change of a correspondingcomponent.

Embodiments include a system comprising: an automation networkcomprising a gateway at a premises, wherein the gateway is coupled to aremote network, wherein the gateway is configured to control a pluralityof components at the premises including at least one of a thermostat anda lock; and a sensor user interface (SUI) coupled to the gateway andpresented to a user via a plurality of remote client devices, whereinthe SUI includes a plurality of display elements for managing andreceiving data of the plurality of components agnostically across theplurality of remote client devices, wherein the plurality of displayelements includes an interactive icon comprising a plurality of controlregions, wherein each control region is configured to control a statechange of a corresponding component.

The plurality of control regions of the interactive icon is configuredto control a plurality of states of the corresponding component.

The interactive icon includes a thermostat icon corresponding to thethermostat, and the plurality of control regions includes a plurality ofquadrants.

Each control region is configured to change a setting of the thermostatin response to an action received in the control region.

The thermostat icon includes a display region configured to display aplurality of state information of the corresponding environmentalcontrol system.

A first quadrant is configured to control an increase in a heat pointsetting of the corresponding thermostat.

A second quadrant is configured to control a decrease in a heat pointsetting of the corresponding thermostat.

A third quadrant is configured to control an increase in a cool pointsetting of the corresponding thermostat.

A fourth quadrant is configured to control a decrease in a cool pointsetting of the corresponding thermostat.

The interactive icon includes a lock icon corresponding to the lock.

Each control region is configured to change a setting of the lock inresponse to an action received in the control region.

The lock icon includes a display region configured to display aplurality of state information of the corresponding lock.

The plurality of control regions includes a first control regionconfigured to toggle a state of the corresponding lock in response to atap received in the first control region.

The plurality of control regions includes a second control regionconfigured to control locking of the corresponding lock in response to atap received in the second control region.

The plurality of control regions includes a third control regionconfigured to control unlocking of the corresponding lock in response toa tap received in the third control region.

The plurality of control regions includes a handle icon.

The plurality of control regions includes a fourth control regionconfigured to control unlocking of the corresponding lock in response todragging and releasing the handle icon in the fourth control region.

The plurality of control regions includes a fifth control regionconfigured to control locking of the corresponding lock in response todragging and releasing the handle icon in the fifth control region.

The plurality of components includes a door, and the interactive iconincludes a door icon corresponding to the door.

Each control region is configured to change a state of the door inresponse to an action received in the control region.

The door icon includes a display region configured to display aplurality of state information of the corresponding door.

The plurality of control regions includes a first control regionconfigured to toggle a state of the corresponding door in response to atap received in the first control region.

The plurality of control regions includes a second control regionconfigured to control closing of the corresponding door in response to atap received in the second control region.

The plurality of control regions includes a third control regionconfigured to control opening of the corresponding door in response to atap received in the third control region.

The plurality of control regions includes a handle icon.

The plurality of control regions includes a fourth control regionconfigured to control opening of the corresponding door in response todragging and releasing the handle icon in the fourth control region.

The plurality of control regions includes a fifth control regionconfigured to control closing of the corresponding door in response todragging and releasing the handle icon in the fifth control region.

The plurality of remote client devices includes one or more of a smartphone, a mobile phone, a cellular phone, a tablet computer, a personalcomputer, and a touchscreen device.

The controlling of the plurality of components at the premises includescontrolling interoperability among the plurality of components.

The gateway is configured using data of the plurality of components.

At least one of the gateway and the plurality of remote devices areconfigured to perform a synchronization to associate the plurality ofremote devices with the plurality of components.

The plurality of remote devices includes applications that receive thedata from and transmit control instructions to the plurality ofcomponents via the gateway.

The plurality of display elements include display elements comprising arepresentation of a floor plan layout of the premises, wherein the floorplan layout includes representations of the plurality of components.

The interactive icon is configured as an overlay on the floor planlayout.

The floor plan layout visually and separately indicates a location and astate of the plurality of components, wherein the state includes currentstate and historical state.

The floor plan layout includes a three-dimensional representation of thefloor plan.

The floor plan layout includes configuration data for each of theplurality of components.

The plurality of components at the premises includes network devices anda security system comprising security system components.

Embodiments include a method comprising configuring an automationnetwork to include a gateway at a premises. The gateway is coupled to aremote network. The method includes configuring the gateway to control aplurality of components at the premises including at least one of athermostat and a lock. The method includes configuring a sensor userinterface (SUI) to include a plurality of display elements for managingand receiving data of the plurality of components agnostically across aplurality of remote client devices. The SUI is coupled to the gatewayand presented to a user via a plurality of remote client devices. Theplurality of display elements includes an interactive icon comprising aplurality of control regions. Each control region is configured tocontrol a state change of a corresponding component.

Embodiments include a method comprising: configuring an automationnetwork to include a gateway at a premises, wherein the gateway iscoupled to a remote network; configuring the gateway to control aplurality of components at the premises including at least one of athermostat and a lock; configuring a sensor user interface (SUI) toinclude a plurality of display elements for managing and receiving dataof the plurality of components agnostically across a plurality of remoteclient devices, wherein the SUI is coupled to the gateway and presentedto a user via a plurality of remote client devices, wherein theplurality of display elements includes an interactive icon comprising aplurality of control regions, wherein each control region is configuredto control a state change of a corresponding component.

The method includes configuring the plurality of control regions of theinteractive icon to control a plurality of states of the correspondingcomponent.

The method includes configuring the interactive icon to include athermostat icon corresponding to the thermostat, and configuring theplurality of control regions to include a plurality of quadrants.

The method includes configuring each control region to change a settingof the thermostat in response to an action received in the controlregion.

The method includes configuring the thermostat icon to include a displayregion configured to display a plurality of state information of thecorresponding environmental control system.

The method includes configuring a first quadrant to control an increasein a heat point setting of the corresponding thermostat.

The method includes configuring a second quadrant to control a decreasein a heat point setting of the corresponding thermostat.

The method includes configuring a third quadrant to control an increasein a cool point setting of the corresponding thermostat.

The method includes configuring a fourth quadrant to control a decreasein a cool point setting of the corresponding thermostat.

The method includes configuring the interactive icon to include a lockicon corresponding to the lock.

The method includes configuring each control region to change a settingof the lock in response to an action received in the control region.

The method includes configuring the lock icon to include a displayregion configured to display a plurality of state information of thecorresponding lock.

The method includes configuring the plurality of control regions toinclude a first control region configured to toggle a state of thecorresponding lock in response to a tap received in the first controlregion.

The method includes configuring the plurality of control regions toinclude a second control region configured to control locking of thecorresponding lock in response to a tap received in the second controlregion.

The method includes configuring the plurality of control regions toinclude a third control region configured to control unlocking of thecorresponding lock in response to a tap received in the third controlregion.

The method includes configuring the plurality of control regions toinclude a handle icon.

The method includes configuring the plurality of control regions toinclude a fourth control region configured to control unlocking of thecorresponding lock in response to dragging and releasing the handle iconin the fourth control region.

The method includes configuring the plurality of control regions toinclude a fifth control region configured to control locking of thecorresponding lock in response to dragging and releasing the handle iconin the fifth control region.

The plurality of components includes a door, and the interactive iconincludes a door icon corresponding to the door.

The method includes configuring each control region to change a state ofthe door in response to an action received in the control region.

The method includes configuring the door icon to include a displayregion configured to display a plurality of state information of thecorresponding door.

The method includes configuring the plurality of control regions toinclude a first control region configured to toggle a state of thecorresponding door in response to a tap received in the first controlregion.

The method includes configuring the plurality of control regions toinclude a second control region configured to control closing of thecorresponding door in response to a tap received in the second controlregion.

The method includes configuring the plurality of control regions toinclude a third control region configured to control opening of thecorresponding door in response to a tap received in the third controlregion.

The method includes configuring the plurality of control regions toinclude a handle icon.

The method includes configuring the plurality of control regions toinclude a fourth control region configured to control opening of thecorresponding door in response to dragging and releasing the handle iconin the fourth control region.

The method includes configuring the plurality of control regions toinclude a fifth control region configured to control closing of thecorresponding door in response to dragging and releasing the handle iconin the fifth control region.

The method includes configuring at least one of the gateway and theplurality of remote devices to perform a synchronization to associatethe plurality of remote devices with the plurality of components.

The plurality of remote devices includes applications that receive thedata from and transmit control instructions to the plurality ofcomponents via the gateway.

The method includes configuring the plurality of display elements toinclude a representation of a floor plan layout of the premises, whereinthe floor plan layout includes representations of the plurality ofcomponents.

As described above, computer networks suitable for use with theembodiments described herein include local area networks (LAN), widearea networks (WAN), Internet, or other connection services and networkvariations such as the world wide web, the public internet, a privateinternet, a private computer network, a public network, a mobilenetwork, a cellular network, a value-added network, and the like.Computing devices coupled or connected to the network may be anymicroprocessor controlled device that permits access to the network,including terminal devices, such as personal computers, workstations,servers, mini computers, main-frame computers, laptop computers, mobilecomputers, palm top computers, hand held computers, mobile phones, TVset-top boxes, or combinations thereof. The computer network may includeone of more LANs, WANs, Internets, and computers. The computers mayserve as servers, clients, or a combination thereof.

The integrated security system can be a component of a single system,multiple systems, and/or geographically separate systems. The integratedsecurity system can also be a subcomponent or subsystem of a singlesystem, multiple systems, and/or geographically separate systems. Theintegrated security system can be coupled to one or more othercomponents (not shown) of a host system or a system coupled to the hostsystem.

One or more components of the integrated security system and/or acorresponding system or application to which the integrated securitysystem is coupled or connected includes and/or runs under and/or inassociation with a processing system. The processing system includes anycollection of processor-based devices or computing devices operatingtogether, or components of processing systems or devices, as is known inthe art. For example, the processing system can include one or more of aportable computer, portable communication device operating in acommunication network, and/or a network server. The portable computercan be any of a number and/or combination of devices selected from amongpersonal computers, personal digital assistants, portable computingdevices, and portable communication devices, but is not so limited. Theprocessing system can include components within a larger computersystem.

The processing system of an embodiment includes at least one processorand at least one memory device or subsystem. The processing system canalso include or be coupled to at least one database. The term“processor” as generally used herein refers to any logic processingunit, such as one or more central processing units (CPUs), digitalsignal processors (DSPs), application-specific integrated circuits(ASIC), etc. The processor and memory can be monolithically integratedonto a single chip, distributed among a number of chips or components,and/or provided by some combination of algorithms. The methods describedherein can be implemented in one or more of software algorithm(s),programs, firmware, hardware, components, circuitry, in any combination.

The components of any system that includes the integrated securitysystem can be located together or in separate locations. Communicationpaths couple the components and include any medium for communicating ortransferring files among the components. The communication paths includewireless connections, wired connections, and hybrid wireless/wiredconnections. The communication paths also include couplings orconnections to networks including local area networks (LANs),metropolitan area networks (MANs), wide area networks (WANs),proprietary networks, interoffice or backend networks, and the Internet.Furthermore, the communication paths include removable fixed mediumslike floppy disks, hard disk drives, and CD-ROM disks, as well as flashRAM, Universal Serial Bus (USB) connections, RS-232 connections,telephone lines, buses, and electronic mail messages.

Aspects of the integrated security system and corresponding systems andmethods described herein may be implemented as functionality programmedinto any of a variety of circuitry, including programmable logic devices(PLDs), such as field programmable gate arrays (FPGAs), programmablearray logic (PAL) devices, electrically programmable logic and memorydevices and standard cell-based devices, as well as application specificintegrated circuits (ASICs). Some other possibilities for implementingaspects of the integrated security system and corresponding systems andmethods include: microcontrollers with memory (such as electronicallyerasable programmable read only memory (EEPROM)), embeddedmicroprocessors, firmware, software, etc. Furthermore, aspects of theintegrated security system and corresponding systems and methods may beembodied in microprocessors having software-based circuit emulation,discrete logic (sequential and combinatorial), custom devices, fuzzy(neural) logic, quantum devices, and hybrids of any of the above devicetypes. Of course the underlying device technologies may be provided in avariety of component types, e.g., metal-oxide semiconductor field-effecttransistor (MOSFET) technologies like complementary metal-oxidesemiconductor (CMOS), bipolar technologies like emitter-coupled logic(ECL), polymer technologies (e.g., silicon-conjugated polymer andmetal-conjugated polymer-metal structures), mixed analog and digital,etc.

It should be noted that any system, method, and/or other componentsdisclosed herein may be described using computer aided design tools andexpressed (or represented), as data and/or instructions embodied invarious computer-readable media, in terms of their behavioral, registertransfer, logic component, transistor, layout geometries, and/or othercharacteristics. Computer-readable media in which such formatted dataand/or instructions may be embodied include, but are not limited to,non-volatile storage media in various forms (e.g., optical, magnetic orsemiconductor storage media) and carrier waves that may be used totransfer such formatted data and/or instructions through wireless,optical, or wired signaling media or any combination thereof. Examplesof transfers of such formatted data and/or instructions by carrier wavesinclude, but are not limited to, transfers (uploads, downloads, e-mail,etc.) over the Internet and/or other computer networks via one or moredata transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When receivedwithin a computer system via one or more computer-readable media, suchdata and/or instruction-based expressions of the above describedcomponents may be processed by a processing entity (e.g., one or moreprocessors) within the computer system in conjunction with execution ofone or more other computer programs.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to.” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “hereunder,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. When theword “or” is used in reference to a list of two or more items, that wordcovers all of the following interpretations of the word: any of theitems in the list, all of the items in the list and any combination ofthe items in the list.

The above description of embodiments of the integrated security systemand corresponding systems and methods is not intended to be exhaustiveor to limit the systems and methods to the precise forms disclosed.While specific embodiments of, and examples for, the integrated securitysystem and corresponding systems and methods are described herein forillustrative purposes, various equivalent modifications are possiblewithin the scope of the systems and methods, as those skilled in therelevant art will recognize. The teachings of the integrated securitysystem and corresponding systems and methods provided herein can beapplied to other systems and methods, not only for the systems andmethods described above.

The elements and acts of the various embodiments described above can becombined to provide further embodiments. These and other changes can bemade to the integrated security system and corresponding systems andmethods in light of the above detailed description.

What is claimed is:
 1. A system comprising: a plurality of premisesdevices located at a premises, wherein at least one of the premisesdevices is associated with a door; and a computing device configured to:cause output of a user interface, wherein the user interface isassociated with the plurality of premises devices, wherein the userinterface comprises a handle icon associated with the door, and whereinthe handle icon comprises a plurality of regions; cause firstmodification, based on a first input comprising a rotational draggingand releasing action in a first region of the plurality of regions ofthe handle icon, of a setting associated with the at least one of thepremises devices associated with the door; and cause secondmodification, based on a second input comprising a rotational draggingand releasing action in a second region of the plurality of regions ofthe handle icon, of the setting associated with the at least one of thepremises devices associated with the door.
 2. The system of claim 1,wherein the plurality of regions comprise quadrants.
 3. The system ofclaim 1, wherein the setting comprises a locking setting.
 4. The systemof claim 3, wherein the plurality of regions comprises five regions. 5.The system of claim 3, wherein the plurality of regions comprises fourregions.
 6. The system of claim 1, wherein the first input causeslocking of the door and the second input causes unlocking of the door.7. The system of claim 1, wherein the setting of at least one of thepremises devices associated with the door comprises an opening settingof the at least one of the premises devices associated with the door. 8.The system of claim 1, wherein the first input causes closing of thedoor and the second input causes opening of the door.
 9. The system ofclaim 1, wherein the computing device is configured to cause output ofthe user interface via one or more of a smart phone, a mobile phone, acellular phone, a tablet computer, a personal computer, or a touchscreendevice.
 10. The system of claim 1, wherein the user interface comprisesa representation of a floor plan layout of a premises, wherein the floorplan layout comprises representations of a plurality of premisesdevices.
 11. The system of claim 10, wherein the plurality of regionscomprise an overlay on the floor plan layout.
 12. The system of claim10, wherein the floor plan layout indicates a location and a state ofthe plurality of premises devices, wherein the state comprises currentstate and historical state.
 13. The system of claim 10, wherein thefloor plan layout comprises a three-dimensional representation of afloor plan.
 14. The system of claim 10, wherein the floor plan layoutcomprises configuration data for each of the plurality of premisesdevices.
 15. The system of claim 1, wherein the computing device isfurther configured to cause modification, based on a third inputcomprising a dragging and releasing action in a third region, of thesetting of the door.
 16. A method comprising: causing output of a userinterface, wherein the user interface is associated with a plurality ofpremises devices, wherein at least one of the plurality of premisesdevice is associated with a door, and wherein the user interfacecomprises a handle icon associated with the door, wherein the handleicon comprises a plurality of regions; causing first modification, basedon a first input comprising a rotational dragging and releasing actionin a first region of the plurality of regions of the handle icon, of asetting associated with the at least one premises device associated withthe door; and causing second modification, based on a second inputcomprising a rotational dragging and releasing action in a second regionof the plurality of regions of the handle icon, of the settingassociated with the at least one premises device associated with thedoor.
 17. The method of claim 16, wherein the plurality of regionscomprise quadrants.
 18. The method of claim 16, wherein the settingcomprises a locking setting.
 19. The method of claim 16, wherein thefirst input causes locking of the door and the second input causesunlocking of the door.
 20. The method of claim 16, wherein the settingassociated with the at least one of the premises devices associated withthe door comprises an opening setting of the door.
 21. The method ofclaim 16, wherein the first input causes closing of the door and thesecond input causes opening of the door.
 22. The method of claim 16,wherein the plurality of regions comprises at least five regions. 23.The method of claim 16, wherein the plurality of regions comprises atleast four regions.
 24. The method of claim 16, wherein the userinterface comprises a representation of a floor plan layout of apremises, wherein the floor plan layout comprises representations of aplurality of premises devices.
 25. A device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the device to: cause output of a userinterface, wherein the user interface is associated with a plurality ofpremises devices, wherein at least one of the plurality of the premisesdevices is associated with a door, and wherein the user interfacecomprises a handle icon associated with the door, wherein the handleicon comprises a plurality of regions; cause first modification, basedon a first input comprising a rotational dragging and releasing actionin a first region of the plurality of regions of the handle icon, of asetting associated with the at least one premises device associated withthe door; and cause second modification, based on a second inputcomprising a rotational dragging and releasing action in a second regionof the plurality of regions of the handle icon, of the settingassociated with the at least one premises device associated with thedoor.
 26. The device of claim 25, wherein the setting comprises alocking setting.
 27. The device of claim 25, wherein the first inputcauses locking of the door and the second input causes unlocking of thedoor.
 28. The device of claim 25, wherein the setting associated withthe at least one premises device associated with the door comprises anopening setting of the door.
 29. The device of claim 25, wherein thefirst input causes closing of the door and the second input causesopening of the door.
 30. The device of claim 25, wherein the pluralityof regions comprise at least four regions.
 31. The device of claim 25,wherein the plurality of regions comprise at least five regions.